# Filebeat input: intentional delay for specific source

**URL:** <https://discuss.elastic.co/t/filebeat-input-intentional-delay-for-specific-source/155124>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 2, 2018, 6:55am UTC](https://discuss.elastic.co/t/filebeat-input-intentional-delay-for-specific-source/155124 "2018-11-02T06:55:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![justinw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justinw/32/40277_2.png) [@justinw](https://discuss.elastic.co/u/justinw)\
**Post date:** [November 2, 2018, 6:55am UTC](https://discuss.elastic.co/t/filebeat-input-intentional-delay-for-specific-source/155124/1 "2018-11-02T06:55:55Z")

</div>

Hi,

Is there a way to intentionally rate limit a certain file (say, one of the matches in the log input pattern /var/log/all-my-services/\*.log)?

The use case is that one service on a shared machines logs so much that it backs up either 1) filebeat/logstash or 2) causes bulk index request failures/retries. Either way, it'd have an adverse affect on the log collection of other services running on the same instance.

Thanks!  
Justin

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [November 2, 2018, 12:21pm UTC](https://discuss.elastic.co/t/filebeat-input-intentional-delay-for-specific-source/155124/2 "2018-11-02T12:21:59Z")

</div>

Hi @justinw,

It is currently no possible to control the throughput of filebeat, there is an open issue for that [https://github.com/elastic/beats/issues/3847](https://github.com/elastic/beats/issues/3847).

In the meantime one thing you can try is to limit the number or processes running with [`max_procs`](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-general-options.html#_literal_max_procs_literal).  
You can also try to limit the resources of the process using features of the operating system like cgroups.

---

<div class="post-metadata">

**Author:** ![justinw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justinw/32/40277_2.png) [@justinw](https://discuss.elastic.co/u/justinw)\
**Post date:** [November 2, 2018, 5:24pm UTC](https://discuss.elastic.co/t/filebeat-input-intentional-delay-for-specific-source/155124/3 "2018-11-02T17:24:54Z")

</div>

Hi @jsoriano,

Thanks for the info. Bummer that ticket is still open. Any idea on when it might get picked up?

Unfortunately cgroups/max\_procs will limit filebeat entirely, when I just want to limit one specific noisy neighbor on the host machine. I appreciate the response though.

Thanks, Justin

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 30, 2018, 5:24pm UTC](https://discuss.elastic.co/t/filebeat-input-intentional-delay-for-specific-source/155124/4 "2018-11-30T17:24:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.