traceparent
The HTTP header defined by Trace Context that carries the trace identifier, parent span identifier and sampling flag between services.
In more detail
Its four parts are separated by dashes, and the final flags say whether the trace was sampled. Gateways and proxies should forward it unchanged so the trace continues across the hop.
Examples
traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01traceparent: 00-216363698b529b4a97b750923ceb3ffd-94b2b8fda02f34a6-01Related terms
- Trace Context — The standard way of passing a trace identifier and parent span identifier from one service to the next, usually in the traceparent header.
- trace — A record of one request’s whole journey through a system, made of nested spans that show where the time went.
- trace ID — An identifier shared by every span and log line belonging to one request, so they can be found together.
- span ID — A unique identifier for one span; each child span records its parent's span ID so the tree can be rebuilt.
- sampling — Recording only some traces to save cost, chosen by a rule such as a percentage or by keeping every error and slow request.
- span — One timed operation within a trace, such as handling a request or running a query, with its start, duration and attributes.
- HTTP header — A named line of metadata in an HTTP message, such as Content-Type: application/json, that describes the body, the caller or how to handle the exchange.
Taught in
- Observability: Logs, Metrics, Traces — Modern API Architecture: REST, GraphQL & gRPC
- Distributed Tracing: OpenTelemetry & Traceparent — Production Full-Stack Engineering
- Full-Stack System Verification: Capstone Integration — Production Full-Stack Engineering
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture
- The Three Signals: Logs, Metrics And Traces — Full-Stack Observability: Metrics, Tracing & Logging
- Traces, Spans And Context Propagation — Full-Stack Observability: Metrics, Tracing & Logging
- Instrumenting A Service With Client Libraries — Full-Stack Observability: Metrics, Tracing & Logging
- Fifteen Traces For Six Bookings: Where Context Was Lost — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Traces From A Script Nobody Touched: Instrumentation Approaches — OpenTelemetry Certified Associate (OTCA) Exam Prep
- A Library That Traces Nothing, Safely: API, SDK And Extension — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Five Characters: Trace Context And Baggage — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Nine Lines, Five Bugs: Configuring The SDK — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Six Launches, No Code Changes: Language Agents — OpenTelemetry Certified Associate (OTCA) Exam Prep
- API And SDK Sprint: Fourteen Predictions — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Maintenance Sprint: Symptoms First — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Forty Four Of Sixty: The Mock And What It Tells You — OpenTelemetry Certified Associate (OTCA) Exam Prep
- The Evening Before: Final Review — OpenTelemetry Certified Associate (OTCA) Exam Prep