copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
Jaeger 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 data as they traverse a distributed system
Download | Jaeger Read the blog post for more details 🌆 Jaeger v1 end-of-life is scheduled for December 31, 2025 Binaries Jaeger binaries are available for macOS, Linux, and Windows
Getting Started | Jaeger 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
Introduction | Jaeger Jaeger is a distributed tracing platform released as open source by Uber Technologies in 2016 and donated to Cloud Native Computing Foundation where it is a graduated project
Introduction | Jaeger 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
Migration to OpenTelemetry SDK | Jaeger For existing applications that are already instrumented with the OpenTracing API, we recommend replacing the Jaeger clients with the corresponding OpenTelemetry SDKs and the OpenTracing shim bridge available in most languages supported by Jaeger
Troubleshooting | Jaeger Jaeger backend is itself a distributed system, composed of different components, potentially running on many hosts It might be the case that one of these moving parts is not working properly, causing spans to not be processed or stored
APIs | Jaeger 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
Deployment | Jaeger Jaeger all-in-one is a special distribution that combines three Jaeger components, collector, and query service UI, in a single binary or container image It is useful for single-node deployments where your trace volume is light enough to be handled by a single instance
Storage Backends | Jaeger 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 with short TTL on trace data (e g two weeks) to save storage costs