...
| library | version | status | notes |
|---|---|---|---|
| zipkin-js | 0.5+ | supported | new Tracer({..., traceId128Bit: true}) |
| pyramid_zipkin | 0.16+ | downgrade | |
| brave | 3.15+/4.9+ | supported/epoch128 | https://github.com/openzipkin/brave/tree/master/brave-core#128-bit-trace-ids |
| spring-cloud-sleuth | 1.0.11+/1.2.6+ | supported/epoch128 | set spring.sleuth.traceId128=true |
| finagle | 0.40+ | downgrade | |
| zipkin-ruby | unsupported | depends on twitter/finagle#565 | |
| ZipkinTracerModule | 3.2+ | supported | Create128BitTraceId(true) |
| zipkin-go-opentracing | 0.2+ | supported | https://godoc.org/github.com/openzipkin/zipkin-go-opentracing#TraceID128Bit |
| akka-tracing | 0.5.2+ | downgrade | |
| wingtips | 0.11.2+ | transparent | |
| jaeger | 0.10+ | downgrade | |
| zipkin4net | 0.4+ | supported |
epoch128
When a trace ID is 128-bits and the first 32 bits are epoch seconds, the ID can be translated into
an Amazon Web Services ID. Tracers who do this can tunnel through ELBs, for example.
...