You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 5, 2024. It is now read-only.
Hi @huntharo a support rep here brought this to our attention. Thanks for the repro case, it will make it easier to triage this issue. Sorry for the troubles
Ok, I see the issue. When we moved our instrumentation from instrumenting @aws-sdk/lib-dynamodb and @aws-sdk/client-dynamodb, we neglected to include checking for a class that gets exported in @aws-sdk/lib-dynamodbDynamoDBDocument. Your wrapper code creates a client from that here.
@huntharo the fix for this has been released in 7.0.1
Thank you! Yup, I have confirmed in my test case app that the issue was resolved and just deployed this to Prod in our app that was using this and confirmed it was resolved there as well with 7.0.1. Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
[email protected]
logs DB access on the Database tab of APM, logging the specific operations, rates, and times[email protected]
logs DB access only as External Services of APMlib-dynamodb
andclient-dynamodb
instrumentation and shifted the responsibility entirely tosmithy-client
: feat: updated aws sdk v3 instrumentation to function with require-in-… #205Expected Behavior
Troubleshooting or NR Diag results
Steps to Reproduce
Your Environment
node:18.17-alpine3.18
Docker imageAdditional context
The text was updated successfully, but these errors were encountered: