Aug 6, 2025 · Distributed tracing observability platforms, such as Jaeger, are essential for modern software applications that are architected as microservices. Jaeger maps the flow of requests and …

Dec 31, 2025 · 🎉 Jaeger v2 is a new major release based on the OpenTelemetry Collector framework. Read the blog post for more details. 🌆 Jaeger v1 has reached end-of-life on December 31, 2025 and …

Nov 12, 2025 · The Jaeger clients have faithfully served our community for several years. We pioneered many new features, such as remotely controlled samplers and per-operation / adaptive sampling, …

This runs the all-in-one configuration of Jaeger (see Architecture) that combines collector and query components in a single process and uses a transient in-memory storage for trace data.

Below, you’ll find information for beginners and experienced Jaeger users. If you can’t find what you are looking for, or have an issue not covered here, we’d love to hear from you.

Jaeger can be deployed either as an all-in-one binary, where all Jaeger backend components run in a single process, or as a scalable distributed system. There are two main deployment options …

Jaeger supports two kinds of trace storage: primary and archive. The primary storage is used as the main storage for all ingested traces, so it requires a highly scalable backend and is typically used …

Surfaced in Jaeger UI as the “Monitor” tab, the motivation for this feature is to help identify interesting traces (e.g. high QPS, slow or erroneous requests) without needing to know the service or operation …

Jaeger v2 is designed to be a versatile and flexible tracing platform. It can be deployed as a single binary that can be configured to perform different roles within the Jaeger architecture.

Jaeger supports various APIs for saving or retrieving trace data. The following labels are used to describe API compatibility guarantees. stable - the API guarantees backwards compatibility.