Course contentsShow
← Cloud and Infrastructure
Lesson 2089 of 2,98944. Observability - TracingFree lesson

Jaeger Overview

Open-source distributed tracing platform: architecture, components, and deployment patterns.

Jaeger Overview

You'll learn what Jaeger is and how its architecture enables distributed tracing at scale.

What is Jaeger?

Jaeger is an open-source, end-to-end distributed tracing platform originally developed by Uber. Think of it as a detective system that follows requests as they travel through your microservices architecture—capturing timing data, relationships, and metadata at each hop. While OpenTelemetry (which you've already learned) defines how to instrument and collect traces, Jaeger is one of the backends that stores, analyzes, and visualizes those traces.

Core Architecture Components

Jaeger's architecture consists of several key pieces:

  • Jaeger Client Libraries: Embedded SDKs that instrument your applications (now largely replaced by OpenTelemetry SDKs)
  • Jaeger Agent: A lightweight daemon deployed alongside your services that batches and forwards spans to collectors
  • Jaeger Collector: Receives spans from agents, validates them, processes them through a pipeline, and writes to storage
  • Storage Backend: Pluggable storage (Cassandra, Elasticsearch, Kafka, or in-memory) where trace data lives
  • Jaeger Query Service: API layer that retrieves traces from storage
  • Jaeger UI: Web interface for searching, filtering, and visualizing traces with service maps and dependency graphs

Deployment Patterns

Jaeger supports multiple deployment models:

  • All-in-one: Single binary for development/testing
  • Production: Separate collector, query, and agent components for scalability
  • Kubernetes Operator: Managed deployment in cloud-native environments

The agent-collector pattern reduces load on your applications—agents handle local buffering while collectors manage batch processing and storage writes.

Key Takeaway:
Jaeger is a complete distributed tracing backend that receives, stores, and visualizes traces, working seamlessly with OpenTelemetry instrumentation to help you understand request flows across microservices.