openzipkin/zipkin

This system is a distributed tracing platform, specifically the Zipkin server and its associated libraries, designed to collect, store, and visualize trace data from various sources. It supports ingesting spans via Kafka, RabbitMQ, ActiveMQ, Pulsar, and Scribe, and persists them in backends like Elasticsearch, OpenSearch, Cassandra, and MySQL. The system provides a modernized server interface with a redesigned UI, health checks, and self-tracing capabilities, all built on a refactored architecture using Armeria and Spring Boot 3.

This period focused on implementing the v2 storage API across backends like Elasticsearch, Cassandra, and MySQL, while migrating the server infrastructure to Armeria and Spring Boot 3. The work also introduced new core domain models, collector components, and a modernized frontend, supported by extensive test coverage.

39 changes

This period focused on consolidating the Zipkin server's architecture by introducing Spring Boot autoconfiguration for various storage backends and collectors, such as Cassandra, Elasticsearch, Kafka, and RabbitMQ. The work also included significant improvements to test coverage, adding comprehensive integration and benchmark tests for these new configurations and existing components.

26 changes

This period focused on standardizing the project's build, deployment, and testing environments through the introduction of portable shell scripts and Docker-based test images. Key additions included support for multi-architecture builds, GPG signing, and new integration test containers for Elasticsearch, OpenSearch, Cassandra, ActiveMQ, and Eureka, alongside a new JUnit 5 testing module and Pulsar collector.

15 changes

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.