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
When I try to extract a b3 tracing id of len 32 (128 bits) it fails to parse it.
dd-trace-go/ddtrace/tracer/textmap.go
Line 337 in a2e9ddd
Reading the specification for the headers it states that the X-B3-TraceId header is encoded as 32 or 16 lower-hex characters. https://github.com/openzipkin/b3-propagation#identifiers
Would be nice if you can support b3 tracing id with 128 bits
The text was updated successfully, but these errors were encountered:
Related to #695
Sorry, something went wrong.
I guess we can close now.
Added issue and PR for supporting for B3 extract for dd-lambda-wrapper: DataDog/datadog-lambda-go#50 (@gbbr, would you like to take a look at it?)
That issue depends on this one. Would be nice if dd-trace/tracer repo can be bumped to make use of this fix :)
No branches or pull requests
When I try to extract a b3 tracing id of len 32 (128 bits) it fails to parse it.
dd-trace-go/ddtrace/tracer/textmap.go
Line 337 in a2e9ddd
Reading the specification for the headers it states that the X-B3-TraceId header is encoded as 32 or 16 lower-hex characters.
https://github.com/openzipkin/b3-propagation#identifiers
Would be nice if you can support b3 tracing id with 128 bits
The text was updated successfully, but these errors were encountered: