OpenTelemetry - XRay does not clearly represents all the services

[bhoradc]

Discussed in #143

^{Originally posted by robvanpamel May 23, 2024}
Hi,

I start to use AWS Messaging in combination with OpenTelemetry and X-Ray. I must admit that i am new to X-Ray so my assumption can be wrong (-used to work with DataDog in the past-).

Let say that i created a producer and a consumer that use SQS as their messaging protocol. Now when the producer publishes a messages, it goes to SQS and their the consumer picks it up to process it.
What I expected to see in X-Ray is

Publisher --> Publish Message --> SQS --> Consumer --> Process Message
However, the semantics of Publisher and Consumer seem to be wiped out although in OpenTelemetry the data is clearly sent to X-Ray (cref: service.name) .
The problem with this solution is that it gives the impression that the Publisher is doing all the work, and the consumer is not involved. Let say that the consumer has dependencies to other services, this will cause a lot of confusion.

How can I create a "X-Ray node" that represent my Consumer / Producer ?

I attached both the logs as well.

trace.subscriber.txt
trace.publisher.txt
x-ray-trace.txt