Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(tracing): adds 128 bit trace id support for b3 and w3c trace he…
…aders (#5434) Currently the trace id component of b3 and w3c headers are truncated from 128bits to 64bits. This was done to make b3 and w3c headers compatible with datadog tracers. Moving forward this is not an acceptable solution. When ``DD_TRACE_128_BIT_TRACEID_GENERATION_ENABLED=True`` the tracer should NOT truncate the trace_id in b3 and w3c headers. The full trace id should be used. ## Checklist - [x] Change(s) are motivated and described in the PR description. - [x] Testing strategy is described if automated tests are not included in the PR. - [x] Risk is outlined (performance impact, potential for breakage, maintainability, etc). - [x] Change is maintainable (easy to change, telemetry, documentation). - [x] [Library release note guidelines](https://ddtrace.readthedocs.io/en/stable/contributing.html#Release-Note-Guidelines) are followed. - [x] Documentation is included (in-code, generated user docs, [public corp docs](https://github.com/DataDog/documentation/)). - [x] Author is aware of the performance implications of this PR as reported in the benchmarks PR comment. ## Reviewer Checklist - [ ] Title is accurate. - [ ] No unnecessary changes are introduced. - [ ] Description motivates each change. - [ ] Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes unless absolutely necessary. - [ ] Testing strategy adequately addresses listed risk(s). - [ ] Change is maintainable (easy to change, telemetry, documentation). - [ ] Release note makes sense to a user of the library. - [ ] Reviewer is aware of, and discussed the performance implications of this PR as reported in the benchmarks PR comment.
- Loading branch information