We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Want to populate a cloud.resource_id attribute for APM spans accessing DynamoDB.
cloud.resource_id
Need to test end-to-end. Scenarios to explicitly test for:
May want to use separate NR accounts for each of the scenarios, to make it easier to see results.
Successful end-to-end solution will require one of either CloudWatch or API Polling to be enabled.
APM Context Team will consume the attribute, generate necessary relationship files to be ingested
N/A
The text was updated successfully, but these errors were encountered:
https://new-relic.atlassian.net/browse/NR-250088
Sorry, something went wrong.
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.
blocked
meiao
Successfully merging a pull request may close this issue.
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:
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
The text was updated successfully, but these errors were encountered: