Changed:Default trace propagation styles to Datadog,tracecontext
#3248
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the release notes
This release changes the default trace propagation style from
Datadog,b3multi,b3
toDatadog,tracecontext
.This aligns the Ruby APM with other APM languages, increasing cross-language compatibility out of the box.
This change also improve interoperability with the W3C tracecontext propagation standard, used by OpenTelemetry systems.
Unless you are using B3 propagation and are not configuring an explicit
DD_TRACE_PROPAGATION_STYLE_EXTRACT
(ortracing.distributed_tracing.propagation_extract_style
), this change will not reduce observability.Otherwise, if you use B3 propagation, you can set the environment variable
DD_TRACE_PROPAGATION_STYLE_EXTRACT=Datadog,b3multi,b3
to restore the previous behavior.For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.