# Memory metrics

**URL:** <https://discuss.elastic.co/t/memory-metrics/57490>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 8, 2016, 3:15pm UTC](https://discuss.elastic.co/t/memory-metrics/57490 "2016-08-08T15:15:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkGavalda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markgavalda/32/4764_2.png) [@MarkGavalda](https://discuss.elastic.co/u/MarkGavalda)\
**Post date:** [August 8, 2016, 3:15pm UTC](https://discuss.elastic.co/t/memory-metrics/57490/1 "2016-08-08T15:15:18Z")

</div>

On Linux (and probably other Unix based) machines it would be great to see more details about the memory metrics: instead of just used/free plus swap it would be good to see buff&caches, shared and available, just like free -h reports. On most Linux servers all free RAM will be used for buffers and caching so free will most likely be reported as almost 0%, when in reality that's not true.

---

<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:** [August 9, 2016, 2:05pm UTC](https://discuss.elastic.co/t/memory-metrics/57490/2 "2016-08-09T14:05:35Z")

</div>

Feel free to open a feature request for this in the beats repo: [https://github.com/elastic/beats](https://github.com/elastic/beats)

---

<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:** [August 29, 2016, 3:15pm UTC](https://discuss.elastic.co/t/memory-metrics/57490/3 "2016-08-29T15:15:29Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.