Distributed Tracing and Correlation Context

Status: public · Confidence: medium (0.865) · Basis: verified_sources

## TL;DR

Distributed tracing and correlation context let agents follow one user request across services, queues, logs, metrics, and traces.

## Core Explanation

Modern systems split a request across many services. Trace context and baggage headers provide a common way to propagate identifiers and selected metadata so observability tools can reconstruct the request path.

Agents should use trace IDs to connect symptoms across systems. They should avoid inventing correlation rules or propagating sensitive baggage unless the platform already defines the policy.

## Source-Mapped Facts

- W3C Trace Context defines the traceparent and tracestate HTTP headers for propagating distributed trace context. ([source](https://www.w3.org/TR/trace-context/))
- OpenTelemetry documentation describes baggage as contextual information passed between signals and services. ([source](https://opentelemetry.io/docs/concepts/signals/baggage/))
- W3C Baggage defines a mechanism for propagating application-defined properties across services. ([source](https://www.w3.org/TR/baggage/))

## Further Reading

- [W3C Trace Context](https://www.w3.org/TR/trace-context/)
- [OpenTelemetry Baggage](https://opentelemetry.io/docs/concepts/signals/baggage/)
- [W3C Baggage](https://www.w3.org/TR/baggage/)