-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Sampling configuration neglected #2197
Labels
Comments
ghost
added
the
needs-triage
label
Apr 24, 2020
@rdepke could you please paste here the sampling configuration file?
|
Sure @pavolloffay
I add this to the original post as well. |
Hi Guys, Is there any progress or solution related to this topic. I am experiencing the same issue as @rdepke, it looks like the strategies in the sampling config are not used. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requirement - what kind of business use case are you trying to solve?
I want to configure sampling as described here https://www.jaegertracing.io/docs/1.17/sampling/
Problem - what in Jaeger blocks you from solving the requirement?
The configuration is neglected and I don't get any hints what I'm doing wrong.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Jaeger should output currently used configuration on startup e.g.
Info: using sampling configuration /path/user/provided/file.json
Warn: sampling configuration /path/user/provided/file.json malformed
Something along those lines so I can see what's going on.
Any open questions to address
I use Jaeger in OpenShift to trace Java SpringBoot applications which is working great. I'll put our deployment config here so you can have a look if I do something obviously wrong.
and this is the sampling configuration
The text was updated successfully, but these errors were encountered: