Currently, the existing --jaeger flag adds trace, span and parent span information to outgoing RPCs.
However it does not set the sampling bit, which means analysing the trace is impossible if the backend infrastructure is not recording the distributed trace.
This new option --force-jaeger-sample ensures that every originating yab RPC is captured, most useful in the single yab (non benchmarking) case.
Currently, the existing --jaeger flag adds trace, span and parent span information to outgoing RPCs.
However it does not set the sampling bit, which means analysing the trace is impossible if the backend infrastructure is not recording the distributed trace.
This new option --force-jaeger-sample ensures that every originating yab RPC is captured, most useful in the single yab (non benchmarking) case.
It uses constSampler with a decision value of true to ensure the sampling bit in the Jaeger headers. See: https://www.jaegertracing.io/docs/1.22/client-libraries/#tracespan-identity