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.

Sign up for GitHub

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

Jump to bottom

Statsd plugin needs read_buffer_size setting. #3189

Closed
kriptor opened this issue Aug 31, 2017 · 3 comments · Fixed by #4598
Closed

Statsd plugin needs read_buffer_size setting. #3189

kriptor opened this issue Aug 31, 2017 · 3 comments · Fixed by #4598
Labels
feature request Requests for new plugin and for new features to existing plugins
Milestone
1.8.0

Comments

@kriptor
Copy link

kriptor commented Aug 31, 2017

It would really be useful if we had a way to set the read buffer size of the statsd input plugin by witch we would have more control over how many metrics per second can be successfully handled without making some obscene system settings of rmem_default. I'm not a GO programmer but it looks pretty straight forward to add this.
@danielnelson danielnelson added the feature request Requests for new plugin and for new features to existing plugins label Aug 31, 2017
@SimonOlenik
Copy link

We need that ASAP!

@borut78
Copy link

borut78 commented Aug 27, 2018

Makes perfect sense to have a setting like this.

@danielnelson danielnelson mentioned this issue Aug 27, 2018
Merged
3 tasks
@danielnelson danielnelson added this to the 1.8.0 milestone Aug 27, 2018
@kriptor
Copy link
Author

kriptor commented Aug 30, 2018

Thx @danielnelson

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Milestone
1.8.0
Development

Successfully merging a pull request may close this issue.

Add read_buffer_size option to statsd input influxdata/telegraf
4 participants
@danielnelson @kriptor @SimonOlenik @borut78