Server extensions and choices

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

    TypeModuleRelated productOther notes
    StorageLogz.ioSupports both sending and reading back data to and from Logz.io: Secure & Scalable Log Management with Cloud-Based ELK
    StorageScouter APMonly supports sending to an Scouter
    StorageApache kafkaSupports aggregation and indexing of tracing data via Kafka Streams State Store.
    ReporterHaystackSupports 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 thesame data sent to the default Zipkin server.

      • When COLLECTOR_ZIPKIN_HTTP_PORT=9411 is set, Jaeger exposes a partial implementation of Zipkin’s HTTP POST endpoints
      • When SPAN_STORAGE_TYPE=kafka and , Jaeger reads Zipkin v1 thrift encoded span messages from a Kafka topic.
        • Note: The above is a deprecated practice in Zipkin. Most instrumentation bundle multiple spans per message in v2 format.
      • Pitchfork exposes the same HTTP POST endpoints Zipkin does
        • http port 9411 accepts /api/v1/spans (thrift, json) and /api/v2/spans (json, proto) POST requests.

    Did we miss a server extension or alternative? Please open a pull-request toopenzipkin.github.io.