Zipkin
Zipkin is an open source distributed tracing system for gathering timing data to troubleshoot latency problems in microservice architectures. It was originally developed at Twitter based on the Google Dapper paper, and is now a CNCF-related project maintained by the OpenZipkin community. Zipkin provides a collector, storage, and query service with a UI for visualizing trace data across distributed services.
APIs
Zipkin API V2
Zipkin's v2 HTTP API for querying and collecting distributed traces. Provides endpoints for submitting spans, querying traces, looking up services and span names, and retrieving...
Capabilities
Distributed Tracing Investigation
A workflow capability for an SRE investigating latency or errors in a distributed system. Combines Zipkin trace search, trace retrieval, and dependency analysis to surface root ...
Run with NaftikoFeatures
End-to-end tracing of requests across microservices.
Ingestion of spans via HTTP, Kafka, and other transports.
Query traces by service, span name, tags, and time range.
Derived service-to-service dependency links from spans.
Web-based UI for exploring traces and dependency graphs.
Pluggable backends including in-memory, MySQL, Cassandra, and Elasticsearch.
Use Cases
Identify slow services and operations in a microservice architecture.
Trace failed requests across services to find error origin.
Visualize which services call which, with call counts.
Identify hotspots and optimize critical-path operations.
Integrations
Java instrumentation library for OpenZipkin.
OpenTelemetry can export traces to Zipkin.
Spring framework integration emitting Zipkin traces.
Span transport via Kafka for asynchronous ingestion.
Storage backend for spans and traces at scale.