Repository navigation
Support undecided observability state #32
Description
Activity
Not quite yet, I think we still want to update the sampler API to produce
UNDECIDEDunless specifically configured. This way requests from non-configurable clients sampled at a higher rate by reconfiguring the target server. Thoughts?I think “undecided” should be used as the default sampler (would not impact WC services)
The default sampler should not cause a local service to observe operations, but it should also not prevent upstream tracing-aware services from recording trace data based on their local sampler configuration. This requires samplers to support an additional undecided state in addition to observed, and not observed.
In practice this should prevent the
X-B3-Sampledfrom being set on outgoing requests.