Zipkin Distributed Tracing

Zipkin is a distributed tracing system that helps gather and analyze timing data needed to troubleshoot latency problems in microservice architectures. Originally developed at Twitter in 2012 and based on the Google Dapper paper, the project is now maintained by the OpenZipkin community under the Apache 2.0 license. The system collects trace data through instrumentation libraries called tracers, with the most popular reporting methods being HTTP and Kafka, though many other transports are supported. Applications need to be instrumented to report trace data, with libraries available for Java through Brave, as well as Python, Go, Ruby, JavaScript, PHP, CSharp, and Scala. The core functionality allows users to jump directly to a trace if they have a trace ID from a log file, or query traces based on attributes including service name, operation name, tags, and duration. The web interface presents detailed timing breakdowns showing the percentage of time spent in each service and whether operations failed, along with a dependency diagram showing how many traced requests flowed between applications to identify aggregate behavior and error paths. Storage backends include in-memory for testing, MySQL, PostgreSQL, Cassandra, and Elasticsearch for production deployments. The system supports both client and server side sampling to control data volume. The project has accumulated over 17,000 GitHub stars and serves as the reference implementation for much of the OpenTelemetry tracing specification, with the Zipkin v2 JSON format widely adopted as an industry standard.