-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
OTel sampler is by default "AlwaysOn" but the documentation states different #12443
Comments
@GFriedrich please open a PR to update the the documentation to match reality. Looks like the docs were not updated when the config was in #9978 |
/triage accpeted |
@strongjz: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/triage accepted |
@strongjz will do. |
It's already set to always on now, though. We'd have to wait till 1.13 to change it. So you could change it to that and update the docs for a 1.13 release. |
@strongjz: Ok then I'll change the default sampler and the documentation. Will work on it on the weekend. |
What happened:
The documentation states that the OTel sampler is by default set to "AlwaysOff". But in fact it is "AlwaysOn".
What you expected to happen:
That the documentation aligns with the code.
IMHO it would be best if the code is changed, because a "AlwaysOn" setting can be somewhat heavy in regards to the amount of created traces.
Anything else we need to know:
Default is configured here:
ingress-nginx/internal/ingress/controller/config/config.go
Line 888 in 5ae018e
But documentation states something different on these places:
ingress-nginx/docs/user-guide/third-party-addons/opentelemetry.md
Line 79 in 5ae018e
ingress-nginx/docs/user-guide/nginx-configuration/configmap.md
Line 167 in 5ae018e
ingress-nginx/docs/user-guide/nginx-configuration/configmap.md
Line 1049 in 5ae018e
The text was updated successfully, but these errors were encountered: