Add span attribute support for AWS_DYNAMO_DB_TABLE

kford-newrelic commented 6 months ago

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[bot] commented 6 months ago

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

kford-newrelic commented 3 months ago

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 commented 1 month ago

Need to implement a new agent API first.

newrelic / newrelic-java-agent