Adrian Cole
Adrian Cole
Along this note, it does seem we need two different or maybe three sections. * users of existing trace instrumentation generally have fewer things to answer.. ex what are usual...
here are some notes about the questions asked on span naming the main concern is that the names are low cardinality (they don't repeat endlessly due to containing variables) ex....
PS context is that google docs aren't addressable in china. office 365 is still dunno doesn't seem culturally well used in open source. etherpad is pretty rad, but not a...
love the discussion here
cc @openzipkin/core @prat0318 @yurishkuro
Forgot one point about response headers. If we added one, we should be careful to document that it might be absent because.. - there was no trace provisioned - a...
I'm in favor of a zipkin-trace-id or similar (esp since http/2 downcases). Reason is that the shape of the ID matters, and I'd want people to confidently paste this into...
here's a quick summary for next person. propagation doesn't always use the same mechanism and some even concatenate things into the same header (ex [TraceContext](https://github.com/TraceContext/tracecontext-spec) does) Best advice to someone...
looks like there's progress on stagemonitor https://github.com/stagemonitor/stagemonitor/pull/254
zipkin support is published with census (dapper successor) starting with version 0.8. Agent support just recently started https://github.com/census-instrumentation/opencensus-java/pull/780