System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) · Lesson

How Distributed Tracing Works

Explore the mechanisms behind distributed tracing, including context propagation across service boundaries. See how requests are tracked through multiple microservices.

How Distributed Tracing Works is a free System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What is Context Propagation?

Imagine a request traveling through many services. How do we know it's all part of the same original operation? This is where context propagation comes in.

It's the mechanism that ensures unique identifiers (like a Trace ID) and other relevant information follow a request as it moves between different services or components.

Without it, each service would start a "new" trace, making it impossible to see the full end-to-end journey.

What is Trace Context?

The "context" being propagated isn't just a single ID. It's a small bundle of information called the trace context.

Trace ID: The unique identifier for the entire request journey.
Span ID: The ID of the current operation within the trace.
Parent Span ID: The ID of the operation that called the current one.
Trace Flags: Information like whether the trace is sampled (should be recorded).

This context is crucial for linking operations together.

Context in HTTP Headers

When services communicate over HTTP, the trace context is typically propagated using special HTTP headers.

The calling service injects the context into the outgoing request's headers. The receiving service then extracts this context from the incoming request's headers.

Common header formats include W3C Trace Context (traceparent, tracestate) and B3 Propagation headers.

Tracing a Service Call

Let's trace a simple request:

User makes a request to Service A.
Service A starts a new trace and span.
Service A calls Service B, injecting its current trace context into the HTTP headers.
Service B receives the request, extracts the context, and creates a new span linked to Service A's span.
Service B may then call Service C, propagating the context further.

This chain allows us to see the full path.

Injecting Context into Requests

Imagine we have a TraceContext object. Before making an HTTP call, we'd inject its details into the request headers. This example simulates adding a traceparent header.

Try running this example:

public class ClientService {
  public static void main(String[] args) {
    String traceId = "a1b2c3d4e5f6g7h8";
    String spanId = "i9j0k1l2m3n4o5p6";
    String traceparentHeader = String.format("00-%s-%s-01", traceId, spanId);

    System.out.println("--- Client Service ---");
    System.out.println("Preparing outgoing request.");
    System.out.println("Injecting trace context into header:");
    System.out.println("  traceparent: " + traceparentHeader);
    System.out.println("Making call to Service B...");
  }
}

Extracting Context from Requests

When Service B receives the request, it looks for these special headers. It then extracts the trace context to understand its place in the overall operation.

This example simulates extracting the traceparent header.

Try running this example:

public class ServerService {
  public static void main(String[] args) {
    // Simulate an incoming request header
    String incomingTraceparent = "00-a1b2c3d4e5f6g7h8-i9j0k1l2m3n4o5p6-01";

    System.out.println("--- Server Service ---");
    System.out.println("Received incoming request.");
    System.out.println("Extracting trace context from header:");
    System.out.println("  traceparent: " + incomingTraceparent);

    // Parse the header (simplified)
    String[] parts = incomingTraceparent.split("-");
    if (parts.length == 4) {
      System.out.println("  Extracted Trace ID: " + parts[1]);
      System.out.println("  Extracted Parent Span ID: " + parts[2]);
    } else {
      System.out.println("  Could not parse traceparent header.");
    }
  }
}

Automated Instrumentation

Manually injecting and extracting context for every call would be tedious and error-prone. This is where instrumentation libraries come in.

These libraries, often part of an observability framework like OpenTelemetry, automatically:

Generate new trace and span IDs.
Inject context into outgoing requests (e.g., HTTP clients).
Extract context from incoming requests (e.g., HTTP servers).
Create new child spans linked to the parent.

They handle the heavy lifting for you!

Beyond HTTP: Other Protocols

While HTTP headers are common, context propagation isn't limited to them. Tracing needs to work across various communication methods:

Message Queues: Context can be added as metadata to messages (e.g., Kafka headers, RabbitMQ properties).
gRPC: Context is propagated via gRPC metadata.
Databases: Sometimes, context can be passed within a database transaction or even as comments in queries for advanced scenarios.

The principle remains the same: pass the trace context along.

Full Request Journey

With proper context propagation, a distributed tracing system can reconstruct the entire journey of a request.

This allows you to visualize:

Which services were involved.
The order of operations.
How long each service took.
Where errors occurred.

This end-to-end visibility is invaluable for debugging and performance optimization in complex microservice architectures.

Propagating the Context

You're building a microservice application. Service A calls Service B, and you want to ensure the trace context is correctly passed between them to link their operations.

Recap: How Tracing Works

In this lesson, we explored the core mechanism behind distributed tracing: context propagation.

Trace context (IDs, flags) is passed between services.
HTTP headers are a common way to propagate context.
Instrumentation libraries automate the injection and extraction of context.
This allows for end-to-end visibility of requests across distributed systems.

Understanding this process is key to leveraging distributed tracing effectively!

Frequently asked questions

Is the “How Distributed Tracing Works” lesson free?

Yes — the full text of “How Distributed Tracing Works” is free to read here on the web, and the System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) course, upgrade to CoddyKit PRO.

What will I learn in “How Distributed Tracing Works”?

Explore the mechanisms behind distributed tracing, including context propagation across service boundaries. See how requests are tracked through multiple microservices. You practise System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)?

No prior experience is required. System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “How Distributed Tracing Works” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) lesson?

Yes. Every System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)