DevOps Glossary

OpenTelemetry Trace Context is the distributed tracing metadata that lets services connect related spans into one end-to-end trace as a request moves through an application. In OpenTelemetry, this context is usually propagated through HTTP headers such as traceparent and tracestate, or through messaging metadata in systems like Kafka and RabbitMQ. It carries identifiers such as the trace ID, span ID, and sampling flags, so a backend service, worker, or downstream API can create the next span under the same trace instead of starting a disconnected one. Teams use trace context to debug latency, follow failures across microservices, connect logs and traces, and understand request paths in Kubernetes, serverless, and cloud-native systems. It depends on consistent instrumentation and propagation across service boundaries; if a proxy, SDK, or custom client drops the headers, the trace can break.