Ask HN: How does your team maintain a high level overview of its microservices?

After working for a while on products built around microservices, I saw repeatedly the issue of not having an easy way to check dependencies between these components or get basic info about them being discussed and raised by teams. Do you know any solution that suit this purpose? A solution that provides a more high level overview of your microservices ecosystem? I know there are tools that "scan" and drew a map of your microservices and inter-dependencies, but I just don't think they're very friendly to use. I also know that is possible to write wiki pages and readme files to describe the microservices, but I don't think this solution is easily searchable/accessible. I was wondering if exist something that can be used more upfront, when the services are being created. Like a service index, for instance. I'd like to hear your experiences if you please.