# Incorrect "system.memory.actual.free" metrics

**URL:** <https://discuss.elastic.co/t/incorrect-system-memory-actual-free-metrics/83783>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [April 27, 2017, 2:05am UTC](https://discuss.elastic.co/t/incorrect-system-memory-actual-free-metrics/83783 "2017-04-27T02:05:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [May 3, 2017, 3:24am UTC](https://discuss.elastic.co/t/incorrect-system-memory-actual-free-metrics/83783/3 "2017-05-03T03:24:39Z")

</div>

This seems to be the same as [Metricbeat system.memory.actual.free - is it accurate?](https://discuss.elastic.co/t/metricbeat-system-memory-actual-free-is-it-accurate/80650), where Metricbeat does not use the `MemAvailable` value from the kernel.

@tim_wong Can you please open a new issue for this in the Github repo so we can track this.

FYI @simonl

---

_[View the full topic](https://discuss.elastic.co/t/incorrect-system-memory-actual-free-metrics/83783)._