Add new span attributes to SQS calls to facilitate entity relationships #2377
Assignees
Labels
points: 5
1-2 weeks
Comments
newrelic-node-agent-team
moved this to Triage Needed: Unprioritized Features
in Node.js Engineering Board
kmudduluru
moved this from Triage Needed: Unprioritized Features
to To do: Features here are prioritized for this sprint (jira for remaining tickets)
in Node.js Engineering Board
jsumners-nr
moved this from To do: Features here are prioritized for this sprint (jira for remaining tickets)
to In progress: Issues being worked on
in Node.js Engineering Board
github-project-automation
bot
moved this from In progress: Issues being worked on
to Done: Issues recently completed
in Node.js Engineering Board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We need to add new span attributes so the cloud monitoring team can link SQS calls from Node.js app to AWS SQS:
Linking between APM and SQS entities is done using the following span attributes:
messaging.system- should be the stringaws_sqscloud.region- the AWS region the queue is in. eg. us-east-2cloud.account.id- the AWS' account id. eg. 123456789012messaging.destination.name- the name of the queue. eg. MyQueuecloud.region,cloud.account.id, andmessaging.destination.namecan be derived from the queue URL. The queue URL follow the format:https://sqs.{region}.amazonaws.com/{account.id}/{queue.name}.Additional context
I don't think these should go into the common attributes here but instead add an after hook to parse the QueueUrl and add the relevant span attributes described above.
The text was updated successfully, but these errors were encountered: