CNCF Jaeger, a Distributed Tracing System
Clone or download
caniszczyk and yurishkuro Add as an adopter (#1121)
#207 (comment)

Signed-off-by: Chris Aniszczyk <>
Latest commit 7d9d212 Oct 16, 2018
Failed to load latest commit information.
.github Add ISSUE_TEMPLATE and PULL_REQUEST_TEMPLATE (#805) May 4, 2018
cmd Change CollectorZipkinHTTPort to CollectorZipkinHTTPPort (#1110) Oct 11, 2018
crossdock Use Go 1.11 in Travis (#1104) Oct 8, 2018
docker-compose Update Dockerfiles to reference executable via ENTRYPOINT (#815) Jul 9, 2018
examples/hotrod Support tracer env based initialization in hotrod (#1115) Oct 12, 2018
idl @ 347af16 Bump idl with zipkin swagger and messaging annos (#533) Nov 13, 2017
jaeger-ui @ d148dc5 Bump UI to latest (#1061) Sep 18, 2018
model Fix import grouping (#1080) Sep 24, 2018
pkg Fix import grouping (#1080) Sep 24, 2018
plugin Refactor es storage (#1111) Oct 12, 2018
scripts Ingester binaries & Docker (#1086) Sep 28, 2018
storage Specify metric name/tags via annotation (#1096) Oct 1, 2018
swagger-gen Collect Zipkin v2 json (#518) Nov 16, 2017
thrift-gen Fix import grouping (#1080) Sep 24, 2018
.codecov.yml Require 100% coverage (#909) Jul 3, 2018
.gitignore Ingester binaries & Docker (#1086) Sep 28, 2018
.gitmodules Update Makefile build_ui target to lerna structure (#798) Jul 18, 2018
.travis.yml Use Go 1.11 in Travis (#1104) Oct 8, 2018 Add as an adopter (#1121) Oct 16, 2018 Specify metric name/tags via annotation (#1096) Oct 1, 2018
CODEOWNERS Add jpkrohling to maintainers / code owners (#851) May 29, 2018 Add CNCF Code of Conduct (#415) Sep 22, 2017 Rename standalone (#1062) Sep 19, 2018 Rearrange info about DCO, add tips for squashing (#953) Jul 24, 2018
DCO Add DCO and updade accordingly Sep 17, 2017 Change maintainer nominations to public (#534) Nov 14, 2017
LICENSE Update to Apache 2.0 License (#391) Sep 9, 2017
Makefile Fix golit link (#1112) Oct 11, 2018 Fix typo (#1025) Aug 27, 2018 Describe release process (#573) Dec 1, 2017
doc.go Finish replacing uber/jaeger with jaegertracing/jaeger (#537) Nov 14, 2017
glide.lock Support tracer env based initialization in hotrod (#1115) Oct 12, 2018
glide.yaml Support tracer env based initialization in hotrod (#1115) Oct 12, 2018

Build Status Coverage Status Gitter chat OpenTracing-1.0 FOSSA Status CII Best Practices

Jaeger - a Distributed Tracing System

Jaeger, inspired by Dapper and OpenZipkin, is a distributed tracing system released as open source by Uber Technologies. It can be used for monitoring microservices-based distributed systems:

  • Distributed context propagation
  • Distributed transaction monitoring
  • Root cause analysis
  • Service dependency analysis
  • Performance / latency optimization

See also:

Jaeger is hosted by the Cloud Native Computing Foundation (CNCF). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Jaeger plays a role, read the CNCF announcement.


High Scalability

Jaeger backend is designed to have no single points of failure and to scale with the business needs. For example, any given Jaeger installation at Uber is typically processing several billions of spans per day.

Native support for OpenTracing

Jaeger backend, Web UI, and instrumentation libraries have been designed from ground up to support the OpenTracing standard.

  • Represent traces as directed acyclic graphs (not just trees) via span references
  • Support strongly typed span tags and structured logs
  • Support general distributed context propagation mechanism via baggage

Multiple storage backends

Jaeger supports two popular open source NoSQL databases as trace storage backends: Cassandra 3.4+ and Elasticsearch 5.x/6.x. There are ongoing community experiments using other databases, such as ScyllaDB, InfluxDB, Amazon DynamoDB. Jaeger also ships with a simple in-memory storage for testing setups.

Modern Web UI

Jaeger Web UI is implemented in Javascript using popular open source frameworks like React. Several performance improvements have been released in v1.0 to allow the UI to efficiently deal with large volumes of data, and to display traces with tens of thousands of spans (e.g. we tried a trace with 80,000 spans).

Cloud Native Deployment

Jaeger backend is distributed as a collection of Docker images. The binaries support various configuration methods, including command line options, environment variables, and configuration files in multiple formats (yaml, toml, etc.) Deployment to Kubernetes clusters is assisted by Kubernetes templates and a Helm chart.


All Jaeger backend components expose Prometheus metrics by default (other metrics backends are also supported). Logs are written to standard out using the structured logging library zap.

Backwards compatibility with Zipkin

Although we recommend instrumenting applications with OpenTracing API and binding to Jaeger client libraries to benefit from advanced features not available elsewhere, if your organization has already invested in the instrumentation using Zipkin libraries, you do not have to rewrite all that code. Jaeger provides backwards compatibility with Zipkin by accepting spans in Zipkin formats (Thrift or JSON v1/v2) over HTTP. Switching from Zipkin backend is just a matter of routing the traffic from Zipkin libraries to the Jaeger backend.

Related Repositories


Instrumentation Libraries



Building From Source





Below are the official maintainers of the Jaeger project. Please use @jaegertracing/jaeger-maintainers to tag them on issues / PRs.

  • @black-adder
  • @jpkrohling
  • @pavolloffay
  • @vprithvi
  • @yurishkuro

Some repositories under jaegertracing org have additional maintainers.

Project Status Bi-Weekly Meeting

The Jaeger contributors meet bi-weekly, and everyone is welcome to join. Agenda and meeting details here.



Questions, Discussions, Bug Reports

Reach project contributors via these channels:


Jaeger as a product consists of multiple components. We want to support different types of users, whether they are only using our instrumentation libraries or full end to end Jaeger installation, whether it runs in production or you use it to troubleshoot issues in development.

Please see for some of the organizations using Jaeger today. If you would like to add your organization to the list, please comment on our survey issue.


Apache 2.0 License.