-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Clarify statsd receiver use case description #33502
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/statsd
Describe the issue you're reporting
The following line is not clear to me:
This seems to be saying that a collector with statsd receiver should run on the same host as a process which emits statsd metrics (this is how I interpret the term "agent"), and have a one-to-one relationship with that process (single input)? The part about not supporting a horizontal pool seems clear that a process should send all of its statsd traffic to a single collector and NOT load balance across multiple.
The text was updated successfully, but these errors were encountered: