Bas van Beek

For that small group of people that want to remain in a mixed instrumentation deployment brownfield we could simply have these propagation mechanisms in contrib repo's; that's what they are...

What are you trying to say with that? The spec is clear on supporting the usage of various propagation methods, just like it says it supports the usage of various...

@tcolgate I guess we agree to disagree Time for others to chime in.

The implementation directly in the go client library will be deprecated in the future, see: https://github.com/census-instrumentation/opencensus-go/pull/790

sorry but error boolean is a terrible idea (error=false anyone)... I'd much rather see the absence or availability of an error key with a string payload like Zipkin which allows...

This is very similar to the problems with OpenTracing's LogEvents. I would appreciate standard middlewares / defaults to not have too many of these elaborate span details as outlined by...

Check out: https://zipkin.io/zipkin-api/#/ And more details / conversations / issues at the API project: https://github.com/openzipkin/zipkin-api

I agree with @bogdandrutu that can better live in the exporter properties. Where I expect default attributes to be of use is in the scope of specific instrumentation (ex. http...

Unfortunately the current implementation of OpenCensus Tracing expects a standard isolated PHP Request lifecycle and is thus incompatible with event driven PHP solutions like ReactPHP. Given enough demand this might...

OpenCensus PHP requires the usage of OpenCensus Agent. Z Pages are available from the Agent. For enabling Z Pages and export to OC Agent, we need the PR #220 merged.