# Metricbeat memory usage

**URL:** <https://discuss.elastic.co/t/metricbeat-memory-usage/254217>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 4, 2020, 7:16am UTC](https://discuss.elastic.co/t/metricbeat-memory-usage/254217 "2020-11-04T07:16:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarophin403](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tarophin403/32/65022_2.png) [@tarophin403](https://discuss.elastic.co/u/tarophin403)\
**Post date:** [November 4, 2020, 7:16am UTC](https://discuss.elastic.co/t/metricbeat-memory-usage/254217/1 "2020-11-04T07:16:53Z")

</div>

Is it normal for a metricbeat process thats runnning as a docker container to record "docker.memory.usage.pct" (one of the data fields collected by metricbeat) with values higher than 100%(1.00067, 1.00044...)?

metricbeat version : 5.6

---

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [November 4, 2020, 3:43pm UTC](https://discuss.elastic.co/t/metricbeat-memory-usage/254217/2 "2020-11-04T15:43:04Z")

</div>

Have you tried if this happens also in newer versions? In case it was an issue, it's very likely it's already fixed in recent versions.

---

<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:** [December 2, 2020, 5:43pm UTC](https://discuss.elastic.co/t/metricbeat-memory-usage/254217/3 "2020-12-02T17:43:04Z")

</div>

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