Feature Request | ServiceMap in X-Ray Tracing does not show EventBridge and SQS
- Dominant language
- JavaScript
- Stars
- 280
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Currently we have following usecase
1. An object upload to the S3 bucket initiates an event.
2. This event places a message onto the SQS queue.
3. The SQS queue, in turn, triggers the associated Lambda function.
While the functionality operates as expected, we've encountered an issue with the AWS X-Ray Trace Map view. The trigger events and SQS are categorized as **clients**, yet the X-Ray details lack the desired depth for these clients. Our objective is to accurately represent the complete flow in the X-Ray Trace Map, including comprehensive details about these clients. Is there a solution to achieve this?
After going through following link https://github.com/aws/aws-xray-sdk-node/issues/445 seems like this feature is not natively supported within AWS. May be a feature Request for future.
Contributor guide
Research direction
Start with the AWS X-Ray SDK for Node.js behavior described here and compare it with aws/aws-xray-sdk-node#445. Trace the S3 → EventBridge → SQS → Lambda flow in the X-Ray Trace Map; done means a concrete, supported path or a scoped SDK feature request for showing EventBridge and SQS details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- distributed-systems, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100