of folks. For many, the MySQL option is a good start, as it is familiar. services: storage: image: openzipkin/zipkin-mysql container_name: mysql ports: - 3306:3306 server: image: openzipkin/zipkin environment: - STORAGE_TYPE=mysql - MYSQL_HOST=mysql ports: - 9411:9411 depends_on: - storage
2012. In 2015, OpenZipkin became the primary fork. OpenZipkin is an org on GitHub. It contains tracers, OpenApi spec, service components and docker images. https://github.com/openzipkin
server spans can share a span ID • Spans are reported in Thrift or Json • Trace identifiers are propagated as X-B3 http headers • This is very important for interop! • Arbitrary baggage is out-of-scope Zipkin defines a span and propagation format.
to (String, String) [BinaryAnnotation] • Tags special-case RPC details such as role and peer • When RPC, start/end events are recorded Mapping OpenTracing to Zipkin Span
a Zipkin system. Support B3. With it, you’ll be compatible with any Zipkin tracer. Remember you are not alone! @adrianfcole #zipkin gitter.im/openzipkin/zipkin zipkin-go-opentracing example