-
Notifications
You must be signed in to change notification settings - Fork 22
Spans not record dynamodb table name #145
Comments
Probably related to newrelic/newrelic-node-apollo-server-plugin#215, let's see if support.newrelic.com can help. |
Hi @jordigh , I can ask for support.newrelic.com, but I think this problem should be because for |
@Blankll if you can provide a code snippet to reproduce the error, it would help us understand the issue much better. |
@Blankll I used your repo. I pared it down to not use lambda to make this easier to triage but also moved some of the require statements around to ensure the agent was loaded first and I see the issue you're describing. I'm going to mark this as a feature request. It doesn't appear to be called out in the README but we do not support extracting |
Note to agent team: We only will set |
Description
We query multi DynamoDB tables within a single Lamba event request by using partiQL though
ExecuteStatementCommand
, and we enabled distributed tracing. NewRelic in DynaomDB call's span fieldb.collection
have no table name.From issue
BatchGetItemCommand
andBatchWriteCommand
may also have this problem, I only testedExecuteStatementCommand
from my side.Expect
In
ExecuteStatementCommand
Span it can record the requested table name like other commands eg. GetItemYour Environment
env: AWS-lambda
Runtime: node-16
NewRelic-AWS Lambda-Layers:
arn:aws:lambda:ap-southeast-2:451483290750:layer:NewRelicNodeJS16X:16
dependencies:
The text was updated successfully, but these errors were encountered: