# Metricbeat system.process.memory.rss.bytes is inflated

**URL:** <https://discuss.elastic.co/t/metricbeat-system-process-memory-rss-bytes-is-inflated/383523>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [November 18, 2025, 9:56pm UTC](https://discuss.elastic.co/t/metricbeat-system-process-memory-rss-bytes-is-inflated/383523 "2025-11-18T21:56:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [November 18, 2025, 9:56pm UTC](https://discuss.elastic.co/t/metricbeat-system-process-memory-rss-bytes-is-inflated/383523/1 "2025-11-18T21:56:28Z")

</div>

Metricbeat 8.5.3 is reporting

rss.bytes almost three time of system installed memory.

why is that? is there explanation about it?

for example exactly at same time -

system.memory.total = 540,665,892,864

and

system.process.memory.rss.bytes = 1,381,122,424,832

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 18, 2025, 10:25pm UTC](https://discuss.elastic.co/t/metricbeat-system-process-memory-rss-bytes-is-inflated/383523/2 "2025-11-18T22:25:01Z")

</div>

> [@elasticforme](#):
>
> Metricbeat 8.5.3 is reporting

This version is almost 3 years old, it may be an issue or bug that was already solved.

Try to upgrade to a recent version to see if this still happens.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [November 18, 2025, 10:27pm UTC](https://discuss.elastic.co/t/metricbeat-system-process-memory-rss-bytes-is-inflated/383523/3 "2025-11-18T22:27:42Z")

</div>

that is biggest issue, to upgrade. LOL
