# Control volume of data sent via filebeat
**URL:** https://discuss.elastic.co/t/control-volume-of-data-sent-via-filebeat/231078
**Category:** Beats
**Tags:** filebeat
**Created:** [May 5, 2020, 5:43am UTC](https://discuss.elastic.co/t/control-volume-of-data-sent-via-filebeat/231078 "2020-05-05T05:43:26Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@gajanan8086](https://discuss.elastic.co/u/gajanan8086)
#### Post date: [May 5, 2020, 5:43am UTC](https://discuss.elastic.co/t/control-volume-of-data-sent-via-filebeat/231078/1 "2020-05-05T05:43:27Z")
Is there a way to control volume of data sent via filebeat? There could be a scenario where a process can spin out of control and generate huge logs/ exceptions. We do not want to send this redundant huge data to elastic cluster and overloading it.
If we had a parameter which could help define threshold on number of lines/ volume of data should be sent per time unit can help us avoid such disasters.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 5, 2020, 5:50am UTC](https://discuss.elastic.co/t/control-volume-of-data-sent-via-filebeat/231078/2 "2020-05-05T05:50:57Z")
There's no way to do this at the moment. Any back pressure that Filebeat might encounter will be from Elasticsearch, which will accept thing as fast as it can.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 2, 2020, 5:51am UTC](https://discuss.elastic.co/t/control-volume-of-data-sent-via-filebeat/231078/3 "2020-06-02T05:51:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.