This is a potential tracer interop chance, provided by Google( @bogdandrutu ), Zipkin ( @adriancole ). It provided a new way to be portable across backends, don't like OpenTracing to provide an APIs layer, but have not to tell what are really happening.
The two major things make the portable possible.
- trace-context format, the new specification, as you known, I already take part in it.
- An exporter mechanism, export means that the data collected by the library can be useful in zipkin or others. Here is the exporter implementations. And the data format is based on trace protobuf definition
So we always want to do some interop works with other tracers, now, we have two choices:
- Support Zipkin v2 network format. Just need a service to receive, buffer, assemble.
- Implement OpenCensus reporter. Do more works at agent(client) side, such as compression, quick group spans in same traces. Those will help the performance and network.
After all, this is only a discussion proposal (TBD), feel free to discuss.
This is a potential tracer interop chance, provided by Google( @bogdandrutu ), Zipkin ( @adriancole ). It provided a new way to be portable across backends, don't like OpenTracing to provide an APIs layer, but have not to tell what are really happening.
The two major things make the portable possible.
So we always want to do some interop works with other tracers, now, we have two choices:
After all, this is only a discussion proposal (TBD), feel free to discuss.