# Filebeat too quick on recovering data

**URL:** https://discuss.elastic.co/t/filebeat-too-quick-on-recovering-data/241133
**Category:** Beats
**Tags:** filebeat
**Created:** [July 14, 2020, 12:41pm UTC](https://discuss.elastic.co/t/filebeat-too-quick-on-recovering-data/241133 "2020-07-14T12:41:19Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [July 15, 2020, 8:11am UTC](https://discuss.elastic.co/t/filebeat-too-quick-on-recovering-data/241133/2 "2020-07-15T08:11:55Z")

</div>

Hi!

Unfortunately it does seem that Filebeat had such a mechanism so far. There is interesting related discussion at [Throttling log output from Filebeat directly?](https://discuss.elastic.co/t/throttling-log-output-from-filebeat-directly/168862/8)

However configuring some network limits may be helpful in your case: [https://www.elastic.co/guide/en/beats/filebeat/master/bandwidth-throttling.html](https://www.elastic.co/guide/en/beats/filebeat/master/bandwidth-throttling.html)

C.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-too-quick-on-recovering-data/241133)._