This message was deleted.

Curious, what is the use case here @User You are tring to figure out if a request is spending more time in SQS/SNS

The goal is just to get automatic context propagation for messages that pass through SQS/SNS. The basic flow of our data is

service1 -> SNS Fans out to multiple -> SQS queue -> service2

afaik, there is almost non-existance support for traces and spans on any messaging pipe -sqs, sns and even kinesis streams. Corresponding issue/s are still open: https://github.com/aws/aws-xray-sdk-python/issues/173 https://github.com/aws/aws-xray-sdk-python/issues?q=is%3Aissue+is%3Aopen+sqs

Gotcha, that makes sense given the lack of examples I could find. I just wanted to make sure it wasn't just my lack of experience in the domain that made me think that it wasn't implemented