Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Validate entity linking for Lambda functions and DynamoDB #2715

Open
mrickard opened this issue Nov 8, 2024 · 1 comment
Open

Validate entity linking for Lambda functions and DynamoDB #2715

mrickard opened this issue Nov 8, 2024 · 1 comment
Assignees
@mrickard
Labels
points: 5 1-2 weeks

Comments

@mrickard
Copy link
Member

mrickard commented Nov 8, 2024 •
edited by svetlanabrennan
Loading

Description

We've added cloud.id and cloud.provider properties to spans and traces for Lambda, and AWS account ID for DynamoDB, so we should verify that they're being processed correctly to link entities in the NR UI.

This work should be done in the node-aws-e2e repo, following the end-to-end testing process there.

Dynamo testing doc notes
@workato-integration
Copy link

https://new-relic.atlassian.net/browse/NR-338310

@newrelic-node-agent-team newrelic-node-agent-team moved this to Triage Needed: Unprioritized Features in Node.js Engineering Board Nov 8, 2024
@mrickard mrickard changed the title Validate entity linking for Lambda functions Validate entity linking for Lambda functions and DynamoDB Nov 8, 2024
@kmudduluru kmudduluru added points: 5 1-2 weeks and removed needs-triage labels Nov 12, 2024
@mrickard mrickard self-assigned this Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrickard mrickard

Labels
points: 5 1-2 weeks
Projects
Node.js Engineering Board
Status: In progress: Issues being worked on
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrickard @kmudduluru