System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) · Lección

Propagación de contexto y baggage

Profundice en la propagación de contexto, un concepto clave de OpenTelemetry para vincular operaciones distribuidas. Explore cómo baggage puede transportar datos arbitrarios entre servicios.

Lección 3 de 411 pasos

Propagación de contexto y baggage es una lección gratuita de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry), y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

Linking Distributed Operations

In modern applications, a single user request often travels through many different services. Imagine an online store: your click goes to a frontend, then an order service, a payment service, and a shipping service.

How do we track this journey? If each service logs independently, it's like trying to follow a single thread in a tangled ball of yarn!

What is Context Propagation?

Context propagation is the magic that links these distributed operations together. It ensures that all parts of a request, no matter which service they touch, share a common understanding of that request.

Think of it like a relay race: the 'baton' (the context) is passed from one runner (service) to the next, linking all their efforts to a single goal.

The Trace Context Explained

The core of context propagation is the Trace Context. This usually contains two vital pieces of information:

  • Trace ID: A unique identifier for the entire request journey across all services.
  • Span ID: A unique identifier for the current operation within a service.

These IDs are crucial for OpenTelemetry to build a complete picture of your request's flow.

How Context Travels

Context doesn't just magically appear! OpenTelemetry uses 'propagators' to inject and extract this context.

Common ways context is propagated:

  • HTTP Headers: Standard headers like traceparent and tracestate.
  • gRPC Metadata: Similar to HTTP headers, but for gRPC calls.
  • Message Queue Properties: When sending messages between services.

These mechanisms ensure the Trace ID and Span ID follow the request.

Injecting Context Demo

When a service makes an outgoing call to another service, the current trace context needs to be 'injected' into the request. This example simulates adding trace context to headers.

import io.opentelemetry.api.trace.Span; 
import io.opentelemetry.api.trace.SpanContext;
import io.opentelemetry.context.Context;
import io.opentelemetry.context.propagation.TextMapSetter;
import java.util.HashMap;
import java.util.Map;

public class ContextInjector {

  public static void main(String[] args) {
    // Simulate an active span context
    SpanContext simulatedSpanContext =
        SpanContext.create(
            "0123456789abcdef0123456789abcdef", // Trace ID
            "fedcba9876543210", // Span ID
            io.opentelemetry.api.trace.TraceFlags.getDefault(),
            io.opentelemetry.api.trace.TraceState.getDefault());
    Span span = Span.wrap(simulatedSpanContext);
    Context context = Context.current().with(span);

    Map<String, String> headers = new HashMap<>();
    TextMapSetter<Map<String, String>> setter = Map::put;

    // OpenTelemetry usually handles this implicitly
    // Here, we simulate injecting context into headers
    // using a simplified representation.
    headers.put("traceparent", "00-" + simulatedSpanContext.getTraceId() + "-" + simulatedSpanContext.getSpanId() + "-01");
    
    System.out.println("Injected Headers:");
    headers.forEach((key, value) -> System.out.println(key + ": " + value));
  }
}

Extracting Context Demo

When a service receives an incoming request, it needs to 'extract' the trace context from the request. This allows it to continue the trace initiated by the upstream service.

import io.opentelemetry.api.trace.SpanContext;
import io.opentelemetry.context.Context;
import io.opentelemetry.context.propagation.TextMapGetter;
import io.opentelemetry.context.propagation.TextMapPropagator;
import io.opentelemetry.sdk.OpenTelemetrySdk;
import java.util.HashMap;
import java.util.Map;

public class ContextExtractor {

  public static void main(String[] args) {
    Map<String, String> incomingHeaders = new HashMap<>();
    incomingHeaders.put("traceparent", "00-112233445566778899aabbccddeeff00-aabbccddeeff0011-01");

    TextMapGetter<Map<String, String>> getter = new TextMapGetter<Map<String, String>>() {
      @Override
      public Iterable<String> keys(Map<String, String> carrier) {
        return carrier.keySet();
      }

      @Override
      public String get(Map<String, String> carrier, String key) {
        return carrier.get(key);
      }
    };

    // In a real app, OpenTelemetry.getGlobalPropagators() would be used
    TextMapPropagator propagator = OpenTelemetrySdk.builder().build()
        .getPropagators().getTextMapPropagator();

    Context extractedContext = propagator.extract(Context.current(), incomingHeaders, getter);
    SpanContext spanContext = Span.fromContext(extractedContext).getSpanContext();

    System.out.println("Extracted Trace ID: " + spanContext.getTraceId());
    System.out.println("Extracted Span ID: " + spanContext.getSpanId());
  }
}

Carrying Extra Data: Baggage

Beyond just trace and span IDs, sometimes you need to carry arbitrary key-value data across services that's relevant to the business logic, but not directly for tracing.

This is where Baggage comes in! It's a collection of key-value pairs that travel alongside the trace context.

Baggage vs. Trace Context

It's important to understand the difference:

  • Trace Context: Essential for linking spans and building the trace graph. It's structural.
  • Baggage: Carries application-specific data. Examples include a user_id, tenant_id, or an A/B test variant. It's informational.

Baggage is propagated using the same mechanisms as trace context (e.g., HTTP headers), often in a header like baggage.

Using Baggage Demo

Here's how you can add an item to Baggage in one part of your application and retrieve it in another, potentially downstream, service. This data travels with the request.

import io.opentelemetry.api.baggage.Baggage;
import io.opentelemetry.context.Context;

public class BaggageUsage {

  public static void main(String[] args) {
    // --- Service A: Add to Baggage ---
    System.out.println("--- Service A ---");
    Context contextWithBaggage = Baggage.current()
        .toBuilder()
        .put("user.id", "12345")
        .put("ab.test.group", "variantA")
        .build()
        .make   Current(); // Make this baggage active in current context

    System.out.println("Added user.id: " + Baggage.current().getEntryValue("user.id"));
    System.out.println("Added ab.test.group: " + Baggage.current().getEntryValue("ab.test.group"));
    
    // Simulate passing context (and thus baggage) to Service B
    // In a real app, this would be via HTTP headers, etc.
    callServiceB(contextWithBaggage);
  }

  public static void callServiceB(Context parentContext) {
    // --- Service B: Retrieve from Baggage ---
    System.out.println("\n--- Service B ---");
    // Activate the context from Service A
    try (io.opentelemetry.context.Scope scope = parentContext.makeCurrent()) {
      Baggage currentBaggage = Baggage.current();
      System.out.println("Retrieved user.id: " + currentBaggage.getEntryValue("user.id"));
      System.out.println("Retrieved ab.test.group: " + currentBaggage.getEntryValue("ab.test.group"));
    }
  }
}

Context Propagation Check

You're debugging a distributed system. A user reports an issue, and you have their user_id. You want to see all logs and traces related to this user across multiple services.

Context & Baggage Summary

You've learned how context propagation is fundamental to distributed tracing, using Trace IDs and Span IDs to link operations across services.

You also explored Baggage, a powerful mechanism to carry custom, application-specific data (like a user_id or A/B test group) alongside your trace context, enriching your observability data.

These concepts are vital for building a complete and actionable view of your distributed applications!

Gratis para empezar

Aprende System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) con un tutor de IA — gratis

Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.

Cursos
12
Lecciones
48

Preguntas frecuentes

¿La lección «Propagación de contexto y baggage» es gratis?

Sí — el texto completo de «Propagación de contexto y baggage» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry), actualiza a CoddyKit PRO. El curso de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) incluye 4 lecciones en total.

¿Qué aprenderé en «Propagación de contexto y baggage»?

Profundice en la propagación de contexto, un concepto clave de OpenTelemetry para vincular operaciones distribuidas. Explore cómo baggage puede transportar datos arbitrarios entre servicios. Practicas System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)?

No se requiere experiencia previa. System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.

¿Cuánto tiempo toma la lección «Propagación de contexto y baggage»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)?

Sí. Cada lección de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Técnicas de auto-instrumentación
  2. Buenas prácticas de instrumentación manual
  3. Propagación de contexto y baggage
  4. Atributos, eventos y estado de spans
← Volver a System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)