Respect parent_sampled decision in propagation_context sentry-trace header #4356
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.
Since we don't automatically have unsampled spans running, this caused a change in behavior when an upstream sampling decision needs to be propagated further downstream.
Explanation of problem
When an incoming trace has
sampled
set to 0 (trace_id-span_id-0
),in the past we would propagate this since we would have an active span/transaction running but just not sampled, so downstream would also receive
trace_id-span_id-0
from that active span.Now, we actually don't have an active span since we don't sample (just how otel works), so instead of sending the
trace_id-span_id-0
as before, we would have senttrace_id-other_span_id
from thepropagation_context
instead.This would cause the downstream service to not receive the
-0
flag and would thus sample independently, which is a regression.