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

OTel sampler is by default "AlwaysOn" but the documentation states different #12443

Open
GFriedrich opened this issue Dec 5, 2024 · 7 comments · May be fixed by #12450
Open

OTel sampler is by default "AlwaysOn" but the documentation states different #12443

GFriedrich opened this issue Dec 5, 2024 · 7 comments · May be fixed by #12450
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@GFriedrich
Copy link

GFriedrich commented Dec 5, 2024

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:

But documentation states something different on these places:

# The available samplers are: AlwaysOn, AlwaysOff, TraceIdRatioBased, Default: AlwaysOff

| [otel-sampler](#otel-sampler) | string | "AlwaysOff" | |

Specifies the sampler to be used when sampling traces. The available samplers are: AlwaysOff, AlwaysOn, TraceIdRatioBased, remote. _**default:**_ AlwaysOff

@GFriedrich GFriedrich added the kind/bug Categorizes issue or PR as related to a bug. label Dec 5, 2024
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Dec 5, 2024
@strongjz
Copy link
Member

strongjz commented Dec 5, 2024

@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

@strongjz
Copy link
Member

strongjz commented Dec 5, 2024

/triage accpeted
/priority backlog

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Dec 5, 2024
@k8s-ci-robot
Copy link
Contributor

@strongjz: The label(s) triage/accpeted cannot be applied, because the repository doesn't have them.

In response to this:

/triage accpeted
/priority backlog

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.

@strongjz
Copy link
Member

strongjz commented Dec 5, 2024

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Dec 5, 2024
@strongjz strongjz added this to the release-1.13 milestone Dec 5, 2024
@k8s-ci-robot k8s-ci-robot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 5, 2024
@GFriedrich
Copy link
Author

@strongjz will do.
Just a question: Wouldn't it be better to set the default sampler to TraceIdRatioBased. I feel like setting it to AlwaysOn for somebody who just deploys it and doesn't check on the defaults this can cause quite some pain in regards to load.

@strongjz
Copy link
Member

strongjz commented Dec 5, 2024

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.

@GFriedrich
Copy link
Author

GFriedrich commented Dec 5, 2024

@strongjz: Ok then I'll change the default sampler and the documentation. Will work on it on the weekend.

@GFriedrich GFriedrich linked a pull request Dec 8, 2024 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

Successfully merging a pull request may close this issue.

3 participants