Ramon
Ramon
The tracing API is targeted to instrumenting code (libraries or applications). Instrumentation shouldn't care about explicit flushing. Flushing has to do with exporting, so I think it logically belongs there....
I think this is language-specific but it doesn't seem strange to me for exporters to have a flush method. Indeed, most of them in Go already do (it just isn't...
Is there any gRPC equivalent?
I don't like the idea of just blocking some arbitrary selection of paths. I think that if we had a better default sampler (per #156) users wouldn't resort to enabling...
@mtwo > For example, seeing traces of Profiler requests to Stackdriver drive me nuts: they're high latency and throw off my views, and I really don't care about their performance....
Updated that PR with a description of Flush.
> OpenCensus officially supports the following tracing backends: Zipkin, Jaeger and Stackdriver. This is an incorrect statement. Zipkin and Jaeger exporters are in-tree to make it easier to develop and...
Interesting idea. I assume you mean annotations on the client-side span (since the server-side span would not known when the response had been received). Why is the server-side span not...
Just to be clear, I'm not proposing that this replace any of the existing tags. I am not proposing to make any changes to the existing spec. I think that...
@rektide OpenCensus handles both stats/metrics and tracing. These are really separate concerns for now. Tags (as contemplated in this issue) are only available in the stats part of OpenCensus and...