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

Support a max bytes per second on beats protocol #662

Closed
gingerwizard opened this issue Jan 7, 2016 · 11 comments
Closed

Support a max bytes per second on beats protocol #662

gingerwizard opened this issue Jan 7, 2016 · 11 comments
Labels
discuss Issue needs further discussion. enhancement libbeat Team:Integrations Label for the Integrations team

Comments

@gingerwizard
Copy link

Currently Filebeat seems to push data to Logstash at the rate it can tail a file. For users where the rate of log generation is variable this can result in high bandwidth utilization - sometimes unacceptably high.

This ticket proposes introducing a max_bytes_per_second setting in the beats protocol to Logstash. If the log files being followed are written at a greater rate than this setting value, Filebeat will throttle the rate at which it tails the log file - potentially resulting in it "falling behind" . In this case periods of lower activity would be used to catch up.

Discussion required as to how this would impact other beats. It may be more appropriate for this to be a Filebeat specific setting e.g. max_read_bytes_per_second.

@gingerwizard gingerwizard added discuss Issue needs further discussion. Filebeat Filebeat labels Jan 7, 2016
@phoenixy2k
Copy link

+1

@biosed
Copy link

biosed commented Jan 7, 2016

+1 this, would be quite handy

@ruflin
Copy link
Collaborator

ruflin commented Mar 15, 2016

For more discussions also see https://github.com/elastic/filebeat/issues/227

@gtt116
Copy link

gtt116 commented Mar 28, 2016

+1 for this, it would be nice to have a QOS.

@ruflin ruflin added libbeat and removed Filebeat Filebeat labels Apr 27, 2016
@harpreet-sawhney
Copy link

+1

1 similar comment
@abhishekjiitr
Copy link

+1

@alexander-marquardt
Copy link

It would be useful to limit the number of events per second that filebeat can send. This would be useful for example if an application server that is monitored by Filebeat starts to generate millions of Errors, which could otherwise overload Logstash and Elastic with a huge spike in traffic. I have seen this exact scenario cause issues while at a client.

@amomchilov
Copy link

@alexander-marquardt Yep, I had the exact same issue. If the connection was ever interuppted, a backlog built up, which was dumped as fast as FileBeat/Elasticserach could negotiate to go, which was way faster than our network infrastructure could take (over 30 Gb/s, IIRC), which overloaded our load balancers. Sad times.

@andresrc andresrc added Team:Integrations Label for the Integrations team and removed Team:Beats labels Mar 6, 2020
@mostlyjason
Copy link

I created a new meta issue to track this. Closing this one in favor of https://github.com/elastic/beats/issues/17716

@amomchilov
Copy link

@mostlyjason "This issue has been moved to a repository you don't have access to."

@mostlyjason
Copy link

@amomchilov posted here #17775

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issue needs further discussion. enhancement libbeat Team:Integrations Label for the Integrations team
Projects
None yet
Development

No branches or pull requests