Clarify statsd receiver use case description

[dyladan]

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.

[github-actions]

Pinging code owners:

• receiver/statsd: @jmacd @dmitryax

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

[github-actions]

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:

• receiver/statsd: @jmacd @dmitryax

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

[jdheyburn]

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