Michael Nikitochkin
Michael Nikitochkin
I think it is similar to https://github.com/opentracing-contrib/nginx-opentracing/issues/157 It is possible to disable opentracing per location.
@cello86 Is it not part of the tracer: zippkin? I think it should be fixed in https://github.com/rnburn/zipkin-cpp-opentracing/blob/a134d5bb073392a0e2fe23c5fe5ef145c2ceb7ea/zipkin/src/zipkin_core_constants.h#L34
According the documentation https://github.com/openzipkin/b3-propagation#debug-flag this flag should be 1 (for debug), or any other value. I think need to request help of `API GW` to have other values for this...
@huangjiecheng Can you make title a bit shorter and move all details in description? I think the options provided through config file and nginx-opentracing could not controll sampling.
Hi @RyanAD any progress on this one?
@RyanAD next steps: - Add changelog line - Rebase and squash against master branch
Need first release a version of Gem with warning message, that `bulkheading` is disabled by default.
@ewalk153 Is it still relevant? There was another change to extract pattern to separate method: https://github.com/Shopify/semian/commit/190ea6e54288da74d1046dae1fb45b90da55e7fe
@byroot @bmansoob @dalehamel I think we don't need semaphores as distributed storage for Circuit breaker, after switching to Thread base web server like Puma and run everything in containers should...
>That's not going to happen for various reasons. And even if we did, we'd at best run two threads per process, rendering an in-memory semaphore entirely useless. I would try...