# Metricbeat - system.memory.actual.used.pct

**URL:** <https://discuss.elastic.co/t/metricbeat-system-memory-actual-used-pct/301035>\
**Category:** Kibana\
**Created:** [March 30, 2022, 7:02am UTC](https://discuss.elastic.co/t/metricbeat-system-memory-actual-used-pct/301035 "2022-03-30T07:02:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt.Wash](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@Matt.Wash](https://discuss.elastic.co/u/Matt.Wash)\
**Post date:** [March 30, 2022, 7:02am UTC](https://discuss.elastic.co/t/metricbeat-system-memory-actual-used-pct/301035/1 "2022-03-30T07:02:04Z")

</div>

Hi,

When i try to find the root cause of a crash using metricbeat field system.memory.actual.used.pct, my dashboard appears to change the values when i filter by host.name for the machine that crashed. Before I filter by the host, the values are much lower, and the higher utilisations are coming from a different host. See attached gif.

Any ideas much appreciated.

![system_memory_actual_used_pct](https://us1.discourse-cdn.com/elastic/original/3X/b/b/bb7d796cec129e6add90a3c810fd6d5090d4c148.gif)

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [March 30, 2022, 10:57am UTC](https://discuss.elastic.co/t/metricbeat-system-memory-actual-used-pct/301035/2 "2022-03-30T10:57:19Z")

</div>

It seems like the heatmap vis is not configured correctly. It's using the "percentage mode" which has a confusing name because what it's doing is that it's taking the current range of the data and treating that as 0-100%. In this mode there is at least one cell in the heatmap colored red no matter the value (e.g. if all values are between 0 and 0.1, then 0.1 is "100%" for the chart).

As `system.memory.actual.used.pct` is already a percentage, this behavior is pretty confusing, the chart should simply configure stable ranges from 0 to 1:

 ![Screenshot 2022-03-30 at 12.55.55](https://us1.discourse-cdn.com/elastic/original/3X/5/5/555b161cbc35ab2e1872019cf57034ff3606453a.png)  
vs  
 ![Screenshot 2022-03-30 at 12.56.42](https://us1.discourse-cdn.com/elastic/original/3X/0/9/09428153b5c1e1210557eefa7adc05bbf081728a.png)

---

<div class="post-metadata">

**Author:** ![Matt.Wash](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@Matt.Wash](https://discuss.elastic.co/u/Matt.Wash)\
**Post date:** [March 30, 2022, 11:59pm UTC](https://discuss.elastic.co/t/metricbeat-system-memory-actual-used-pct/301035/4 "2022-03-30T23:59:07Z")

</div>

excellent. I swapped it for the custom ranges and it appears to be performing better.

---

<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:** [April 27, 2022, 11:59pm UTC](https://discuss.elastic.co/t/metricbeat-system-memory-actual-used-pct/301035/5 "2022-04-27T23:59:27Z")

</div>

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