Dimitrios Kouzis-Loukas
Dimitrios Kouzis-Loukas
> There's probably a need for a 3rd error strategy - to succeed if at least one tracer succeeds, because the user code might be checking the error and not...
Bringing https://github.com/opentracing/specification/issues/28#issuecomment-270272213 here... > I think this approach will help upgrade or switch systems, though in practice it might require complete deployment across the entire architecture before you switch off...
> The main advantage I see is actually for 3rd-party OSS/etc projects... @bensigelman Awesome - that wasn't clear for me > without making assumptions about the environments they're integrated into....
> If someone manages to make a Multiplexing tracer Exactly - the question is - does OT impose some constraints that prevent such a tracer from being possible? My guess...
P.S. I realize that it's mostly talking and thinking here. I think I will try to write/plug a mixing tracer next time I have time to play with Zipkin-Python-OT
There's a first ugly throw-away C++ draft of some concepts [here](https://github.com/jquinn47/opentracing-cpp/pull/1/files#diff-508ef3931701de6a0923c94032844994).
A warning isn't that useful from my viewpoint, cause this is a "user profile". It's not something exceptional. What I see as viable is something along the lines of a...
> Do you actually have a trace with 800k spans :) Yes... I don't remember if it's multi-parent one. It's 680 Mb (!!) We also have a "full-trace" with 20k...
> Would you be able to list, possibly with numbers and to whom it is relevant, how a trace looks like in this case? Some ballpark numbers out of an...