-
Notifications
You must be signed in to change notification settings - Fork 162
Closed
Labels
blockedThis item's progress is blocked by external dependency or reasonThis item's progress is blocked by external dependency or reasonbug-upstreamThis item is related to a bug caused by upstream dependencyThis item is related to a bug caused by upstream dependencytracerThis item relates to the Tracer UtilityThis item relates to the Tracer Utility
Description
Description of the feature request
Problem statement
SQS currently don't propagate properly traces when chaining Lambda. See aws/aws-xray-sdk-node#208 for more details.
Summary of the feature
- Implement a mechanism to detect when event coming from SQS and contains XRay trace id.
- Rebuild segments to be part of the main trace
Code examples
I did a first implem here : https://github.com/flochaz/x-ray-lambda-sqs-lambda/blob/main/lib/lambda/consumer-function/index.js
Benefits for you and the wider AWS community
The issue on xray sdk has been open for 2 years, people are getting really frustrated, 84 👍 and tens of comments ....
Describe alternatives you've considered
Wait for service team to fix it :)
dreamorosi, renatoargh and RaphaelManke
Metadata
Metadata
Assignees
Labels
blockedThis item's progress is blocked by external dependency or reasonThis item's progress is blocked by external dependency or reasonbug-upstreamThis item is related to a bug caused by upstream dependencyThis item is related to a bug caused by upstream dependencytracerThis item relates to the Tracer UtilityThis item relates to the Tracer Utility