Server extensions and choices

Server extensions

Zipkin server bundles extension for span collection and storage. By default spans can be collected over http, Kafka or RabbitMQ transports and stored in-memory or in MySQL, Cassandra or Elasticsearch.

The following modules add storage or transport extensions to the default server build. Please refer to their individual documentation for setup and configuration guides.

Supported

The following extensions are supported by the Zipkin team. You can reach out to the team on Gitter chat.

Type Module Related product Other notes
Collector zipkin-aws collector-sqs AWS SQS  
Collector zipkin-aws collector-kinesis AWS Kinesis  
Storage zipkin-aws storage-elasticsearch-aws AWS Elasticsearch Service  
Storage zipkin-aws storage-xray AWS X-Ray only supports sending to an XRay UDP daemon
Storage zipkin-gcp storage-stackdriver GCP Stackdriver only supports sending to an Stackdriver

Community supported

Type Module Related product Other notes
Storage zipkin-scouter storage-scouter Scouter APM only supports sending to an Scouter
Storage zipkin-storage-kafka Apache kafka Supports aggregation and indexing of tracing data via Kafka Streams State Store.
Reporter spring-cloud-sleuth-haystack-reporter Haystack Supports sending data to Haystack, a resilient, scalable tracing and analysis system.

Alternative servers

The OpenZipkin team publish apis, data formats, and shared libraries that allow alternate backends to process the same data sent to the default Zipkin server.

Community supported

Listed below are alternative backends that accept Zipkin format. Some use the same code as Zipkin on the same endpoints while others are on alternative endpoints or partially support features. In any case, the following aim to allow existing zipkin clients to use backends the OpenZipkin team does not support. Hence, direct questions to their respective communities.

Did we miss a server extension or alternative? Please open a pull-request to zipkin-website.