Skip to content
This repository has been archived by the owner on Jun 5, 2024. It is now read-only.

AWS SDK v3 DynamoDB - [email protected] (v7.0.0 of this lib) no longer record DynamoDB on Databases APM tab #208

Closed
huntharo opened this issue Sep 15, 2023 · 5 comments · Fixed by #209
Assignees
Labels

Comments

@huntharo
Copy link

Description

Expected Behavior

  • DynamoDB access should be logged in detail on the Database tab of APM

Troubleshooting or NR Diag results

Steps to Reproduce

Your Environment

  • Node version: 16.17.1
  • Operating System and version: Mac OS X and node:18.17-alpine3.18 Docker image

Additional context

@workato-integration
Copy link

@bizob2828
Copy link
Member

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

@bizob2828 bizob2828 self-assigned this Sep 15, 2023
@bizob2828
Copy link
Member

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-dynamodb DynamoDBDocument. Your wrapper code creates a client from that here.

@bizob2828
Copy link
Member

@huntharo the fix for this has been released in 7.0.1

@huntharo
Copy link
Author

@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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
2 participants