-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
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
Issue with @opentelemetry/instrumentation-aws-sdk when tracing sqs and tracestate is empty #1528
Comments
@carolabadeer would you mind looking into this one? |
Hi @bradleyquinn140, thanks for raising this issue. I will work on reproducing it on my end and post my findings here |
Thanks @carolabadeer have you had any luck with this? |
@bradleyquinn140 I tried reproducing the issue but couldn't get to a point where I see this error on my end, can you please provide a simple reproduction? Also curious, what's the use case for having an empty trace state? Does this only happen with SQS? |
After trying quite a few workarounds, I was able to fix this issue by using preRequestHook option in the aws sdk instrumentation. For all AWS SQS requests that are being traced, have a non empty trace state by default:
Hope this helps someone :) |
What version of OpenTelemetry are you using?
As far as I can see I'm using the latest version(s)
What version of Node are you using?
v16.20.0
What did you do?
tracestate
(ie the internal representation is an empty map).@opentelemetry/instrumentation-aws-sdk
enabled.What did you expect to see?
No error messages from the aws sdk
What did you see instead?
Additional context
I'm not sure if the issue is in this package or in the tracestate implementation (if I'm wrong sorry, I'll raise it in
open-telemetry/opentelemetry-js
)It seems like sqs does not allow empty attributes ... from here
Which doesn't seem like it will work with the
traceState
implementation egThe text was updated successfully, but these errors were encountered: