observability

Trace ID Propagation

A single trace ID flows through all services handling a request — enabling end-to-end correlation.

traces0
avg spans/trace0
Generates a distributed trace across services
Click "Simulate Request" to generate traces

How It Works

  • First service generates unique trace ID
  • Trace ID propagated via headers (traceparent)
  • Each service creates a span with parent reference
  • Spans collected centrally for visualization

Use Cases

  • Jaeger, Zipkin, OpenTelemetry
  • Debugging latency across services
  • Finding bottlenecks in request flow
  • Service dependency mapping