- 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
- Introduction | Jaeger
Below, you’ll find information for beginners and experienced Jaeger users If you cannot find what you are looking for, or have an issue not covered here, we’d love to hear from you
- Getting Started | Jaeger
Historically, the Jaeger project supported its own SDKs (aka tracers, client libraries) that implemented the OpenTracing API As of 2022, the Jaeger SDKs are no longer supported, and all users are advised to migrate to OpenTelemetry
- 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
- Monitoring Jaeger
Jaeger itself is a distributed, microservices based system If you run it in production, you will likely want to setup adequate monitoring for different components, e g to ensure that the backend is not saturated by too much tracing data
- 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
|