openzipkin /zipkin

Zipkin is a distributed tracing system

★ 17,473⑂ 3,096👁 654⑃ 2,436● 1,346▤ 100
JavaApache-2.0Created 2012-06-06zipkin.io/
Download: 3.6.13.6.1 ↓3.6.12026-04-08
+0
Daily
17,473
stars
3,096
forks
654
watchers
2,436
prs
1,346
issues
100
releases

README

zipkin





Zipkin is a distributed tracing system. It helps gather
timing data needed to troubleshoot latency problems in service architectures.
Features include both the collection and lookup of this data.

If you have a trace ID in a log file, you can jump directly to it. Otherwise,
you can query based on attributes such as service, operation name, tags and
duration. Some interesting data will be summarized for you, such as the
percentage of time spent in a service, and whether operations failed.



The Zipkin UI also presents a dependency diagram showing how many traced
requests went through each application. This can be helpful for identifying
aggregate behavior including error paths or calls to deprecated services.



Application’s need to be “instrumented” to report trace data to Zipkin. This
usually means configuration of a tracer or instrumentation library. The most
popular ways to report data to Zipkin are via http or Kafka, though many other
options exist, such as Apache ActiveMQ, gRPC, RabbitMQ and Apache Pulsar. The data served to
the UI is stored in-memory, or persistently with a supported backend such as
Apache Cassandra or Elasticsearch.

 Quick-start

The quickest way to get started is to fetch the latest released server as a self-contained
executable jar. Note that the Zipkin server requires minimum JRE 17+. For example:

bash
curl -sSL https://zipkin.io/quickstart.sh | bash -s
java -jar zipkin.jar


You can also start Zipkin via Docker.
bash
 Note: this is mirrored as ghcr.io/openzipkin/zipkin
docker run -d -p 9411:9411 openzipkin/zipkin


Once the server is running, you can view traces with the Zipkin UI at http://localhost:9411/zipkin.

If your applications aren't sending traces, yet, configure them with Zipkin instrumentation or try one of our examples.

Check out the zipkin-server documentation for configuration details, or Docker examples for how to use docker-compose.

 Zipkin Slim

The slim build of Zipkin is smaller and starts faster. It supports in-memory and Elasticsearch storage, but doesn't support messaging transports like Kafka or RabbitMQ. If these constraints match your needs, you can try slim like below:

Running via Java:
bash
curl -sSL https://zipkin.io/quickstart.sh | bash -s io.zipkin:zipkin-server:LATEST:slim zipkin.jar
java -jar zipkin.jar


Running via Docker:
bash
 Note: this is mirrored as ghcr.io/openzipkin/zipkin-slim
docker run -d -p 9411:9411 openzipkin/zipkin-slim


Running via Homebrew:
bash
brew install zipkin
 to run in foreground
zipkin
 to run in background
brew services start zipkin


 Core Library
The core library is used by both Zipkin instrumentation and the Zipkin server.

This includes built-in codec for Zipkin's v1 and v2 json formats. A direct dependency on gson
(json library) is avoided by minifying and repackaging classes used. The result is a 155k jar which
won't conflict with any library you use.

Ex.
java
// All data are recorded against the same endpoint, associated with your se

Top issues

Latest release

3.6.1 3.6.1 2026-04-08
What's Changed
 Switch to recently released docker images by @codefromthecrypt in https://github.com/openzipkin/zipkin/pull/3824
 Add flatten-maven-plugin for Sonatype Central Portal by @codefromthecrypt in https://github.com/openzipkin/zipkin/pull/3825
 Remove outdated BOM warning from dependencyManagement by @codefromthecrypt in https://github.com/openzipkin/zipkin/pull/3826
 Update Netty to 4.2.12.Final by @reta in https://github.com/openzipkin/zipkin/pull/3831
 Bump armeria to 1.38.0 by @AlexKolpa in https://github.com/openzipkin/zipkin/pull/3830

 New Contributors
 @AlexKolpa made

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON