openzipkin/zipkin
This system is a distributed tracing platform that ingests, stores, and queries trace data from various message brokers and storage backends. It provides a server interface for collecting spans via HTTP, gRPC, and protocols like Kafka, RabbitMQ, and Scribe, while supporting storage in Elasticsearch, MySQL, and Cassandra. The architecture includes a modernized UI, health monitoring, and self-tracing capabilities, all built on a refactored core with standardized build and test infrastructure.
46.2
Weak · 1 August 2026
45k
lines of production code
Java
with TypeScript, JavaScript
2
bus factor · 213 authors in all
2
measurements over time
How it got here
2015–2018 · v2 model and storage modernization
This period focused on modernizing the Zipkin codebase by introducing the v2 data model and refactoring storage backends like Elasticsearch, Cassandra, and MySQL to support it. The architecture was significantly updated with a new HTTP server using Armeria, a restructured collector subsystem, and a frontend migration to Vite, while adding comprehensive test coverage for these changes.
37 changes
2019 · Spring Boot autoconfiguration and observability
This period focused on modernizing the Zipkin server by introducing Spring Boot autoconfiguration for all major storage backends and collectors, significantly reducing manual setup requirements. Concurrently, the project expanded its observability and reliability features by adding Prometheus metrics endpoints, health check endpoints, and request throttling to prevent over-capacity issues. The work was heavily supported by comprehensive integration and benchmark tests to ensure the correctness and performance of these new configurations.
26 changes
2020–2025 · Build system standardization and test infrastructure expansion
This period focused on standardizing the build and CI infrastructure through a suite of portable shell scripts for Docker, Maven, and GPG signing. Simultaneously, the project significantly expanded its test environment by introducing dedicated Docker images for various storage backends and message brokers, alongside new JUnit 5 integration testing tools.
17 changes
Survey your own repository
openzipkin/zipkin was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 878ce2a1fa — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.