-
Notifications
You must be signed in to change notification settings - Fork 56
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
Filebeat message rate limit or throttle #395
Comments
Thanks for your input. I think we should handle this on the server side. |
This(throttling) already happens but does not bring much. https://docs.graylog.org/en/latest/pages/sending_data.html#input-throttling My node journal is filled because of the load and speed with which the messages get from filebeat+sidecars and then the message ingress moves to the second node and so forth. Both GL nodes and the agent host are CPU skyrocketing during this initial state of ingress. |
What works today and would aid on the agent side of the problem is to set 1 core And reported here |
That's the kind of throttling I'm referring to, yes. |
I see, it's the 3rd criteria point that would be used for this case. https://docs.graylog.org/en/latest/pages/sending_data.html#throttling-criteria
Still it would be nice to be able to change this value of 20k mess/sec |
Looks like Elastic fixed it. From Filebeat 7.11 onward there is a new message limit that you can set. |
"Events that exceed the rate limit are dropped" |
See Graylog2/graylog2-server#6939
The text was updated successfully, but these errors were encountered: