# MetricBeat and FileBeat CPU overhead

**URL:** <https://discuss.elastic.co/t/metricbeat-and-filebeat-cpu-overhead/72215>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [January 19, 2017, 7:31pm UTC](https://discuss.elastic.co/t/metricbeat-and-filebeat-cpu-overhead/72215 "2017-01-19T19:31:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rherr63](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@rherr63](https://discuss.elastic.co/u/rherr63)\
**Post date:** [January 19, 2017, 7:31pm UTC](https://discuss.elastic.co/t/metricbeat-and-filebeat-cpu-overhead/72215/1 "2017-01-19T19:31:27Z")

</div>

Looking to deploy MetricBeat and FileBeat on potentially 1000's of AWS Linux EC2 instances. Is there a published CPU overhead number for each of these agents? Obviously, developers are concerned about the agentry consuming too much of the CPU. Secondly, how much can it change based on configuration parameters within metricbeat.yml? Trying to get a worst case scenario for example if most of system module metrics are enabled: cpu, memory, processes, etc.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [January 23, 2017, 8:23am UTC](https://discuss.elastic.co/t/metricbeat-and-filebeat-cpu-overhead/72215/2 "2017-01-23T08:23:57Z")

</div>

We don't have any published values as this depends on lots of different parameters.

For filebeat it heavily depends on how many log events you have per second and also the way you configured it. For metricbeat the period on how often events are sent is important, but also the rest of the config. And obviously the size of your EC2 instance.

I strongly recommend you to do some tests in a near production envrionment to get the numbers for your use case. Base on this we potentially can also recommend some config improvements etc. if needed. But that only works if you have all your numbers together.

---

<div class="post-metadata">

**Author:** ![rherr63](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@rherr63](https://discuss.elastic.co/u/rherr63)\
**Post date:** [January 27, 2017, 5:00pm UTC](https://discuss.elastic.co/t/metricbeat-and-filebeat-cpu-overhead/72215/3 "2017-01-27T17:00:51Z")

</div>

> [@ruflin](#):
>
> We don't have any published values as this depends on lots of different parameters.
> 
> For filebeat it heavily depends on how many log events you have per second and also the way you configured it. For metricbeat the period on how often events are sent is important, but also the rest of the config. And obviously the size of your EC2 instance.
> 
> I strongly recommend you to do some tests in a near production envrionment to get the numbers for your use case. Base on this we potentially can also recommend some config improvements etc. if needed. But that only works if you have all your numbers together.

ok, thank you for your input. We are in the process of defining some use case tests.

---

<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:** [February 24, 2017, 5:01pm UTC](https://discuss.elastic.co/t/metricbeat-and-filebeat-cpu-overhead/72215/4 "2017-02-24T17:01:31Z")

</div>

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