search

aws / aws-app-mesh-roadmap

AWS App Mesh is a service mesh that you can use with your microservices to manage service to service communication
Apache License 2.0
347 stars 25 forks source link

Feature Request: Way to enable tracing on the default *.amazonaws.com cluster #308

Open lavignes opened 3 years ago

lavignes commented 3 years ago

If you want to see App Mesh implement this idea, please upvote with a :+1:.

Tell us about your request Today, App Mesh conveniently adds a egress cluster to allow outbound traffic to *.amazonaws.com:443. This saves from having to manually model AWS service endpoints in a mesh.

Unfortunately the route to this cluster is a TCP route in the Envoy TCP proxy filter. The TCP proxy in Envoy does not emit traces, so useful stats about HTTP calls to *.amazonaws.com endpoints do not show up in tools like X-Ray.

It would be great if App Mesh could make it so calls to AWS services show up by default (or with a small amount of configuration) in traces.

Which integration(s) is this request for? All platforms.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Seeing my calls to AWS services show up in my traces by default.

Are you currently working around this issue? Today this can be worked around by manually modeling each AWS service as a VirtualService + VirtualNode in my mesh.

bigdefect commented 3 years ago

Via #310 we may end up turning this into a more general mechanism for introducing TCP traffic traces without application instrumentation. Instrumenting the application is still recommended, but there may be an opportunity to get something out of the box once we know where the traffic is going.

It depends on what the investigation surfaces for this issue's original problem.