Adrian Cole

> > The main advantage I see is actually for 3rd-party OSS/etc projects that > are used by *many* organizations and need to provide tracing > instrumentation without making assumptions...

This is more a task of instrumentation, and it is hard to understand what numbers are good considering the design of the tracer library impacts efficiency. One way is to...

and another note, even brave will be far less efficient than native agents like instana for example, which will very very unlikley use OT for things like servlet instrumentation. It...

you could also do a similar comparison with other agents like elasticsearch's as at least that one supports a garbage-free (mostly) design and is OSS cc also @felixbarny

I completely disagree especially in Java about having to retain a lookup table for scope references. this adds debt which turns to permanent debt once you go v1. can you...

folks @pavolloffay seems reluctant to fix the instrumentation he made and wants to force brave to implement this dodgy api instead. Can we please get this removed?

@codingfabian @raphw are either of you in love with this api that requires implementations to track and try to return scope instances? If you are can you please comment why?...

@pavolloffay your comment was that existing instrumentation are broken. you wrote the instrumentation leading to that issue. fixing the version

What was the outcome of your call? ps on your point about "Having ScopeManager.active() around can be very helpful when instrumenting libraries that have no context or similar to store...

I'm not sure why there is a concept of removing active scope in favor of span.. why this is somehow experimental. This was in use in brave and also census...