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.

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

Add span attribute support for AWS_DYNAMO_DB_TABLE #1802

Closed
kford-newrelic opened this issue Mar 18, 2024 · 3 comments · Fixed by #2113 · May be fixed by #1868
Closed

Add span attribute support for AWS_DYNAMO_DB_TABLE #1802

kford-newrelic opened this issue Mar 18, 2024 · 3 comments · Fixed by #2113 · May be fixed by #1868
Assignees
Labels
3 Story Point Estimate oct-dec qtr Represents proposed work item for the Oct-Dec quarter

Comments

@kford-newrelic
Copy link
Contributor

Description

Want to populate a cloud.resource_id attribute for APM spans accessing DynamoDB.

Acceptance Criteria

Need to test end-to-end. Scenarios to explicitly test for:

  • APM application+updated agent (but AWS CloudWatch and API Polling not enabled)
  • APM application+updated agent (AWS CloudWatch enabled)
  • APM application+updated agent (API Polling)
  • APM application+non updated agent (eg: the cloud.resource_id attribute is missing)

May want to use separate NR accounts for each of the scenarios, to make it easier to see results.

Design Consideration/Limitations

Successful end-to-end solution will require one of either CloudWatch or API Polling to be enabled.

Dependencies

APM Context Team will consume the attribute, generate necessary relationship files to be ingested

Additional context

N/A

@workato-integration
Copy link

@kford-newrelic kford-newrelic added estimate Issue needing estimation apr-jun qtr Represents proposed work item for the Apr-Jun quarter 3 Story Point Estimate and removed estimate Issue needing estimation labels Mar 18, 2024
@kford-newrelic
Copy link
Contributor Author

Auto-discovery for the AWS account is still being discussed. Reflecting this as blocked, since it will take a while to get that challenge sorted out.

@kford-newrelic kford-newrelic added blocked Indicates the issue is currently blocked and not able to proceed and removed apr-jun qtr Represents proposed work item for the Apr-Jun quarter labels Jun 26, 2024
@kford-newrelic
Copy link
Contributor Author

Need to implement a new agent API first.

@kford-newrelic kford-newrelic added oct-dec qtr Represents proposed work item for the Oct-Dec quarter and removed blocked Indicates the issue is currently blocked and not able to proceed labels Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 Story Point Estimate oct-dec qtr Represents proposed work item for the Oct-Dec quarter
Projects
Status: Code Complete/Done
2 participants