Bug: Disconnected trace Spans/ Segments for Calls in App Mesh

[gurudatta-carbon]

SECURITY NOTICE: If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.

Summary

• Current Setup is Virtual Gateway ---Gateway Route --> Virtual Service ------> Virtual Router ----- Virtual Route --> Virtual Node. ---> ECS (Envoy Side car, app container with Otel Agent, Otel Collector Side Car)
  • Otel collector has a xray receiver --> Otlp Exporter (Central collector) ---> xray server
• Same setup causes Spans to be disconnected for HTTP/ HTTP2/ GRPC calls
  • They show up as Client --> Virtual Gateway Envoy Span (Twice , one for span receive and another for gateway route resolution) -> Virtual Node Span (&&) Client --> ECS Service Span
• Expected Behavior: Client --> Virtual Gateway Envoy Span -> Virtual Node Span -> ECS Service Span
• Observing same behavior for calls within services inside mesh as well

Steps to Reproduce

• Setup is described above in summary and for reproducing as well

Are you currently working around this issue?

• N/A Additional context

Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)