We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All of our lambda logs have the trace.id property set to any empty string instead of the actual trace ID.
trace.id
Use the node newrelic lambda layer to lambda layer and ship logs to newrelic.
Logs should contain trace.id property that actually contains the ID of the corresponding trace.
Node v18 Lambda layer version: NewRelicNodeJS18X:48
NewRelicNodeJS18X:48
I noticed this comment in the code:
newrelic-lambda-extension/telemetry/client.go
Line 300 in 88b35fe
I'm wondering if that's the source of the problem. Is there a workaround or way to fix this?
The text was updated successfully, but these errors were encountered:
https://new-relic.atlassian.net/browse/NR-328305
Sorry, something went wrong.
chaudharysaket
No branches or pull requests
Description
All of our lambda logs have the
trace.id
property set to any empty string instead of the actual trace ID.Steps to Reproduce
Use the node newrelic lambda layer to lambda layer and ship logs to newrelic.
Expected Behavior
Logs should contain
trace.id
property that actually contains the ID of the corresponding trace.Your Environment
Node v18
Lambda layer version:
NewRelicNodeJS18X:48
Additional context
I noticed this comment in the code:
newrelic-lambda-extension/telemetry/client.go
Line 300 in 88b35fe
I'm wondering if that's the source of the problem. Is there a workaround or way to fix this?
The text was updated successfully, but these errors were encountered: