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

Clarify statsd receiver use case description #33502

Open
dyladan opened this issue Jun 11, 2024 · 4 comments
Open

Clarify statsd receiver use case description #33502

dyladan opened this issue Jun 11, 2024 · 4 comments
Labels
documentation Improvements or additions to documentation receiver/statsd statsd related issues Stale waiting-for-code-owners

Comments

@dyladan
Copy link
Member

dyladan commented Jun 11, 2024

Component(s)

receiver/statsd

Describe the issue you're reporting

The following line is not clear to me:

Use case: it does not support horizontal pool of collectors. Desired work case is that customers use the receiver as an agent with a single input at the same time.

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.

@dyladan dyladan added the needs triage New item requiring triage label Jun 11, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@jdheyburn
Copy link

I'd be interested in understanding why this receiver was written with this constraint. There are other StatsD aggregators such as telegraf which do not have this stipulation.

@jmacd @dmitryax

Copy link
Contributor

github-actions bot commented Dec 2, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation receiver/statsd statsd related issues Stale waiting-for-code-owners
Projects
None yet
Development

No branches or pull requests

4 participants