Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preparing release v0.23.0 #415

Merged
merged 5 commits into from
Jun 13, 2024
Merged

Preparing release v0.23.0 #415

merged 5 commits into from
Jun 13, 2024

Conversation

biosvs
Copy link
Contributor

@biosvs biosvs commented Jun 13, 2024

No description provided.

jquirke and others added 5 commits May 31, 2024 11:02
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
Add an option to force capture of Jaeger traces
@biosvs biosvs merged commit 915ecc3 into master Jun 13, 2024
6 checks passed
@biosvs biosvs deleted the vitalii/release-0-23-0 branch June 13, 2024 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants