We stand with our friends and colleagues in Ukraine.
To support Ukraine in their time of need
Download
Jaeger components can be downloaded in two ways:
Try Jaeger v2 🎉
November 12, 2024: Jaeger v2 is a new major release based on the OpenTelemetry Collector framework. 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. The table below lists the available binaries:
| Latest version | Assets |
|---|---|
| 2.7.0 | |
| 1.70.0 |
You can find the binaries for previous versions on the GitHub releases page .
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 jaegertracing/jaeger:2.7.0 --help$ podman run quay.io/jaegertracing/jaeger:2.7.0 --help | 2.0 |
| all-in-one | v1 | Designed for quick local testing. It launches the Jaeger UI, collector, query, and agent, with an in-memory storage component. $ docker run jaegertracing/all-in-one:1.70.0 --help$ podman run quay.io/jaegertracing/all-in-one:1.70.0 --help | 0.8 |
| example-hotrod | v1 | Sample application “HotROD ” that demonstrates features of distributed tracing (blog post ). $ docker run jaegertracing/example-hotrod:1.70.0 --help$ podman run quay.io/jaegertracing/example-hotrod:1.70.0 --help | 1.6 |
| jaeger-collector | v1 | Receives spans from agents or directly from clients and saves them in persistent storage. $ docker run jaegertracing/jaeger-collector:1.70.0 --help$ podman run quay.io/jaegertracing/jaeger-collector:1.70.0 --help | 0.8 |
| jaeger-query | v1 | Serves Jaeger UI and an API that retrieves traces from storage. $ docker run jaegertracing/jaeger-query:1.70.0 --help$ podman run quay.io/jaegertracing/jaeger-query:1.70.0 --help | 0.8 |
| jaeger-ingester | v1 | An alternative to collector; reads spans from Kafka topic and saves them to storage. $ docker run jaegertracing/jaeger-ingester:1.70.0 --help$ podman run quay.io/jaegertracing/jaeger-ingester:1.70.0 --help | 1.7 |
| jaeger-remote-storage | v1 | 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 $ docker run jaegertracing/jaeger-remote-storage:1.70.0 --help$ podman run quay.io/jaegertracing/jaeger-remote-storage:1.70.0 --help | 1.37 |
| spark-dependencies | v1 | 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-operator | v1 | A Kubernetes Operator for packaging, deploying, and managing Jaeger installation. | 1.6 |
| jaeger-cassandra-schema | v1 | A utility script used to initialize Cassandra keyspace and schema. $ docker run jaegertracing/jaeger-cassandra-schema:1.70.0 --help$ podman run quay.io/jaegertracing/jaeger-cassandra-schema:1.70.0 --help | 0.8 |
| jaeger-es-index-cleaner | v1 | A utility script used to purge old indices from Elasticsearch, since ES does not support data TTL. $ docker run jaegertracing/jaeger-es-index-cleaner:1.70.0 --help$ podman run quay.io/jaegertracing/jaeger-es-index-cleaner:1.70.0 --help | 1.3 |
| 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 jaegertracing/jaeger-agent:1.62 --help$ podman run quay.io/jaegertracing/jaeger-agent:1.62 --help | 0.8 |
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]
