# Filebeat CPU utilization metrics are not normalized by default

**URL:** https://discuss.elastic.co/t/filebeat-cpu-utilization-metrics-are-not-normalized-by-default/210659
**Category:** Beats
**Tags:** elastic-stack-monitoring
**Created:** [December 5, 2019, 9:24am UTC](https://discuss.elastic.co/t/filebeat-cpu-utilization-metrics-are-not-normalized-by-default/210659 "2019-12-05T09:24:00Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [December 9, 2019, 9:24pm UTC](https://discuss.elastic.co/t/filebeat-cpu-utilization-metrics-are-not-normalized-by-default/210659/2 "2019-12-09T21:24:31Z")

</div>

I'm not sure I'm following.

I answered [Elasticsearch CPU utilization metrics are normalized by default](https://discuss.elastic.co/t/elasticsearch-cpu-utilization-metrics-are-normalized-by-default/210660) but assumed you were talking about cpu percentage differences between what you see in Stack Monitoring and what you see in the Infra UI (or, what you see in `.monitoring-es-*` documents versus what you see in `metricbeat-*` documents).

Did I assume correctly? Or are you talking about monitoring Filebeat within the Stack Monitoring UI?

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-cpu-utilization-metrics-are-not-normalized-by-default/210659)._