Kong Mesh Trouble-shooting

At present, when, we have a problem that occurs in any of the services, the debugging workflow is hard.

We need to identify the listeners in Envoy Config, Look at the routes and then the Clusters and check if there are time-outs/other configurations in these elements etc.

What I would like is the following

Given a Starting Service and a Destination Service

I would like to have a Command Line tools that acts a a combination of traceroute and maven effective-pom. I.e. it informs me

* Whether it is possible to reach the destination from Origin
* A config dump (Full Envoy and CP Elements) or just the configured elements like timeouts, idle timeouts, Circuit breaker settings if any, etc for each segment in the path from Origin Service to Destination Service