Experiment/evaluate distributed tracing frameworks

[gyuho]

#5425 (comment)

Jaeger's instrumentation library is OpenTracing. (OpenTracing is a project specifically designed to provide a single instrumentation API that couples to a variety of tracing systems... zipkin, jaeger, various commercial vendors, etc)

[xiang90]

/cc @dvonthenen

[tedsuo]

Just to add some clarity: The OpenTracing API is just an standardized API layer. Many tracers support it, so it is possible to "instrument once" with OpenTracing, then pick which tracing system you wish to use at runtime. So this would allow etcd to change tracing systems (and support multiple systems) without needing to re-instrument.

API docs: godoc.org/github.com/opentracing/opentracing-go

[davidvonthenen]

@gyuho @xiang90 @tedsuo I actually have quite a bit of familiarity with Jaeger, Zipkin, and OpenTracing. As a user, I have been evaluating them for some time now. I have done some basic implementation with tracing requests among microservices. If you need help with this, let me know.

[gyuho]

Closing. We will improve current metrics/logging first. And consider tracing support.

[vaastav]

Are there any plans of adding tracing support to etcd in the near future?