-
Notifications
You must be signed in to change notification settings - Fork 42
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
Support for extraction of B3 headers #50
Comments
Would also be good to bump dd-trace-go/tracer to get support for 128 bits B3 trace ids |
Hi @stroem, sorry for the late replay. We haven't prioritized any work on adding this to datadog-lambda-go, but we will continue to leave the issue open and see if it gains enough community attention. We would be happy to look at a PR adding b3 header support. |
@purple4reina was this fixed in #150? |
Hey @stroem – sorry for taking so long to take a look at this. -- edit: Wow, our docs our outdated, I'm going to pass it on to our team! I found the Go specific doc which suggests that you can indeed just use -- As per the tracing propagation style docs I noticed this is not inherently available yet in Datadog's Go tracer. For us to better triage this issue, please make sure to submit a feature request ticket in our support platform mentioning this ticket – you could also submit a ticket in the tracer's repository. Since this Library depends on tracing propagation from it, it's best to address it there! I'm going to close the ticket, but feel free to re-open if you have any questions, or concerns! |
Would like to have support for extracing incomming B3 headers.
Current solution only parses xray and datadog trace id and span id.
Suggestion is to use the implementation found in dd-trace-go/tracer using env variables
DD_PROPAGATION_STYLE_EXTRACT
The text was updated successfully, but these errors were encountered: