Validate incoming W3C trace context with a standard propagator and apply an explicit tracestate and sampling policy at public ingress.
Design customer support lookup and fallback steps for trace IDs that were sampled out, never ingested, or removed by retention.
Locate telemetry loss with per-boundary flow evidence, queue age and a known canary while accounting for retries, filtering and temporality.
Keep customer identifiers out of third-party requests by applying destination-aware baggage policy before HTTP instrumentation injects headers.
Distinguish a non-recording remote context from the recording and sampling decisions of the local child span.
