Closed kford-newrelic closed 1 day ago
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
https://new-relic.atlassian.net/browse/NR-250088
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
Need to implement a new agent API first.
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