Download
π Jaeger v2 is a new major release based on the OpenTelemetry Collector framework. For details, read the blog post.
π Jaeger v1 reached end-of-life on December 31, 2025 and will no longer receive updates.
Jaeger v2 components can be downloaded in two ways:
Binaries
Jaeger binaries (including tools/utilities) are available for macOS, Linux, and Windows on the GitHub releases page.
| Latest version | Assets |
|---|---|
| 2.15.0 |
Container images
The following container images are available for the Jaeger project via the jaegertracing organization on Docker Hub and Quay.io:
| Image | Major | Description | Since version |
|---|---|---|---|
| jaeger | v2 | The only binary you need to run Jaeger v2. $ docker run cr.jaegertracing.io/jaegertracing/jaeger:2.15.0 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger:2.15.0 --help | 2.0 |
| example-hotrod | v2 | $ docker run cr.jaegertracing.io/jaegertracing/example-hotrod:2.15.0 --help
$ podman run cr.jaegertracing.io/jaegertracing/example-hotrod:2.15.0 --help | 1.6 |
| jaeger-remote-storage | v2 | A service that implements the Remote Storage API on top of another supported backend. Can be used to share a single-node storage backend, like memory, across multiple Jaeger processes.$ docker run cr.jaegertracing.io/jaegertracing/jaeger-remote-storage:2.15.0 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-remote-storage:2.15.0 --help | 1.37 |
| spark-dependencies | v2 | An Apache Spark job that collects Jaeger spans from storage, analyzes links between services, and stores them for later presentation in the Jaeger UI | 1.3 |
| jaeger-cassandra-schema | v2 | A utility script used to initialize Cassandra keyspace and schema. $ docker run cr.jaegertracing.io/jaegertracing/jaeger-cassandra-schema:2.15.0 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-cassandra-schema:2.15.0 --help | 0.8 |
| jaeger-es-index-cleaner | v2 | A utility script used to purge old indices from Elasticsearch, since ES does not support data TTL. $ docker run cr.jaegertracing.io/jaegertracing/jaeger-es-index-cleaner:2.15.0 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-es-index-cleaner:2.15.0 --help | 1.3 |
| jaeger-collector | v1 | β Deprecated ππ€. Latest available version is 1.76. Receives spans from agents or directly from clients and saves them in persistent storage. $ docker run cr.jaegertracing.io/jaegertracing/jaeger-collector:1.76 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-collector:1.76 --help | 0.8 |
| jaeger-query | v1 | β Deprecated ππ€. Latest available version is 1.76. Serves Jaeger UI and an API that retrieves traces from storage. $ docker run cr.jaegertracing.io/jaegertracing/jaeger-query:1.76 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-query:1.76 --help | 0.8 |
| jaeger-ingester | v1 | β Deprecated ππ€. Latest available version is 1.76. An alternative to collector; reads spans from Kafka topic and saves them to storage. $ docker run cr.jaegertracing.io/jaegertracing/jaeger-ingester:1.76 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-ingester:1.76 --help | 1.7 |
| jaeger-agent | v1 | β Deprecated ππ€. Latest available version is 1.62. Receives spans from Jaeger clients and forwards to collector. Designed to run as a sidecar or a host agent. jaeger-agent is deprecated and no longer recommended for use, see https://github.com/jaegertracing/jaeger/issues/4739. $ docker run cr.jaegertracing.io/jaegertracing/jaeger-agent:1.62 --help
$ podman run cr.jaegertracing.io/jaegertracing/jaeger-agent:1.62 --help | 0.8 |
| jaeger-operator | v1 | β Deprecated ππ€. Latest available version is 1.65. A Kubernetes Operator for packaging, deploying, and managing Jaeger installation. | 1.6 |
Debug and Snapshot Images
The images listed above are the primary release versions. Most components have additional images published:
${component}-debugincludes Delve debugger${component}-snapshotpublished from the tip of the main branch for every commit, allowing testing of unreleased versions${component}-debug-snapshotsnapshot with debugger
Artifact Checksums
Along with the binaries published via GitHub Releases we provide the checksum files, *.sha256sum.txt,
for each of the target architecture archive. Below is an example of validating darwin-amd64 binaries for release v1.39.0:
- download
jaeger-1.39.0-darwin-amd64.sha256sum.txt - download
jaeger-1.39.0-darwin-amd64.tar.gz
# expand the archive
$ tar -xz jaeger-1.39.0-darwin-amd64.tar.gz
# find checksum for hotrod example
$ grep hotrod jaeger-1.39.0-darwin-amd64.sha256sum.txt
5088bcd396351edebf9280ee4d5d0f89f4839ecd64a8711e91a22dea6ddb719c *jaeger-1.39.0-darwin-amd64/example-hotrod
# regenerate the checksum from the binary and compare
$ shasum -b -a 256 jaeger-1.39.0-darwin-amd64/example-hotrod
5088bcd396351edebf9280ee4d5d0f89f4839ecd64a8711e91a22dea6ddb719c *jaeger-1.39.0-darwin-amd64/example-hotrod
Signed Artifacts
We also publish cryptographic signatures for each of the artifact archives. The signatures can be verified using the public key below.
Import the key
$ gpg --import <<EOF
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEY2vAvBYJKwYBBAHaRw8BAQdALagKKnO7ZKHAmPrwEJinKjBHUwMMvtFJLe2h
fcaXbga0QUphZWdlciBUcmFjaW5nIEFydGlmYWN0IFNpZ25pbmcgPGphZWdlci10
cmFjaW5nQGdvb2dsZWdyb3Vwcy5jb20+iJoEExYKAEICGwMFCwkIBwIDIgIBBhUK
CQgLAgQWAgMBAh4HAheAFiEEvQsCYBTHJSYclHiHtC0dsPB5aQ8FAmNrwSsFCRLM
A28ACgkQtC0dsPB5aQ9mcgEA066QypWZZeRrqb6tUxraFfPjPFHvJB+aM4HoieHx
h+4BAKyw584zjoeZRokEO5wkHgWcghtpJ+x7ogDh5T01fdEAuDgEY2vAvBIKKwYB
BAGXVQEFAQEHQPCkvs+pcAQ31FXZBK50MO0/fDHnEpyNzBZZCCWXizE/AwEIB4h+
BBgWCgAmFiEEvQsCYBTHJSYclHiHtC0dsPB5aQ8FAmNrwLwCGwwFCQPCZwAACgkQ
tC0dsPB5aQ9zwQD+NzLramrEK61hdin8MJbJzY7LO1slF81QzaeOae5u5KABAJLq
ZVSFq/hy7CXjmjwVnfo0WEuNyzo/sGSmEQa8gWYH
=B/tl
-----END PGP PUBLIC KEY BLOCK-----
EOF
gpg: key B42D1DB0F079690F: public key "Jaeger Tracing Artifact Signing <jaeger-tracing@googlegroups.com>" imported
gpg: Total number processed: 1
gpg: imported: 1
Verify signature
From the release page (TODO: provide link and fix versions):
- Download
jaeger-1.39.4-darwin-amd64.tar.gz - Download
jaeger-1.39.4-darwin-amd64.tar.gz.asc
Use gpg --verify {signature-file} file, e.g.:
$ gpg --verify jaeger-1.39.4-darwin-amd64.tar.gz.asc jaeger-1.39.4-darwin-amd64.tar.gz
gpg: Signature made Wed Nov 9 13:34:17 2022 EST
gpg: using EDDSA key BD0B026014C725261C947887B42D1DB0F079690F
gpg: Good signature from "Jaeger Tracing Artifact Signing <jaeger-tracing@googlegroups.com>" [ultimate]
