Joshua MacDonald

It's worth examining where this problem comes from. We have a situation in which (all for good reason): (1) Tracer implementations hide the structural details of their SpanContext (2) Carrier/Format...

+1 to coupling the format and carrier arguments. Note I proposed a slightly different approach than Yuri later in the same thread. ᐧ On Wed, Dec 7, 2016 at 5:38...

There aren't enough custom formats and carriers to make that argument. ᐧ

@yurishkuro Related discussion in a C++ PR here: https://github.com/opentracing/opentracing-cpp/pull/6 I never answered your question--why I'd introduce a `CarrierInjector` type. I was thinking of whether I could derive a new kind...

Since my opinions were mentioned above, I'll gladly list them. 1. I wouldn't assume that a log statement's namespace equals the span or tracer's component. Imagine trying to single out...

At my former company, we had a mapping from j.u.l.Level values onto the integers [0, 1200] and then mapped from other languages/logging-library levels onto the roughly-corresponding values. I'm not sure...

Is there some reason to call this "priority" instead of "severity"? I feel that severity is more appropriate. ᐧ On Thu, Apr 6, 2017 at 6:17 PM, 吴晟 Wu Sheng...

Yes, but the two words have different meanings and if these are the same concept, one of the words should be preferred. Moreover, there are conventions around what these words...

An optional tag to indicate the programmer's desire to start a trace makes some sense, in as much as it doesn't muddy OT semantics. I also agree that more relationship...

> OTLP as it stands is not performant/cost efficient enough for capturing all data Lightstep will corroborate this statement. Customers are looking to Sampling today as an approach to lowering...