Welcome to Jaeger’s documentation portal! 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, inspired by Dapper and OpenZipkin, is a distributed tracing system released as open source by Uber Technologies. It is used for monitoring and troubleshooting microservices-based distributed systems, including:
- Distributed context propagation
- Distributed transaction monitoring
- Root cause analysis
- Service dependency analysis
- Performance / latency optimization
Uber published a blog post, Evolving Distributed Tracing at Uber, where they explain the history and reasons for the architectural choices made in Jaeger. Yuri Shkuro, creator of Jaeger, also published a book Mastering Distributed Tracing that covers in-depth many aspects of Jaeger design and operation, as well as distributed tracing in general.
- OpenTracing compatible data model and instrumentation libraries
- Uses consistent upfront sampling with individual per service/endpoint probabilities
- Multiple storage backends: Cassandra, Elasticsearch, memory.
- System topology graphs
- Adaptive sampling (coming soon)
- Post-collection data processing pipeline (coming soon)
See Features page for more details.
- Backend components implemented in Go
- Supported storage backends:
- Cassandra 3.4+
- Elasticsearch 5.x, 6.x, 7.x
- memory storage
See running a docker all in one image.