[mmclean]

OpenCensus [1] provides an implementation for tracing and app-level metrics, a context wire protocol, and exporters for various backends. While it provides similar tracing APIs to OpenTracing, they're not identical, though there have been some early conversations about resolving this.

I'm the PM for Census at Google, though other vendors are involved as well. Basic implementations for Java and Go are already functional, with much more to come. We gave a small talk at Kubecon last month, but will start promoting the project once it's slightly more mature.

[1] http://opencensus.io/

[puzzle]

This discussion goes into more detail about commonalities and differences between the two:

https://github.com/census-instrumentation/opencensus-java/is...

The use case of non-request metrics is the biggest difference to me. While it's great to track e.g. resource usage for each incoming request, there are also workloads that don't fit that mold. Think of a garbage collecting background worker: either you use a separate API to push the data or you make up bogus GC RPCs to attach metrics to their traces.

[daenney]

I have to say, after reading through that, I'm still not quite mystified as to what the differences are.

[tedsuo]

Yes!! We are very interested in resolving these API differences. In my opinion OpenCensus is great and if it could become the “standard” client for OpenTracing it would make me really happy.