# What version of gosigar does Metricbeat 6.4.3 pull in?

**URL:** <https://discuss.elastic.co/t/what-version-of-gosigar-does-metricbeat-6-4-3-pull-in/243757>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 4, 2020, 5:31pm UTC](https://discuss.elastic.co/t/what-version-of-gosigar-does-metricbeat-6-4-3-pull-in/243757 "2020-08-04T17:31:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mehagar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehagar/32/73330_2.png) [@mehagar](https://discuss.elastic.co/u/mehagar)\
**Post date:** [August 4, 2020, 5:31pm UTC](https://discuss.elastic.co/t/what-version-of-gosigar-does-metricbeat-6-4-3-pull-in/243757/1 "2020-08-04T17:31:58Z")

</div>

I'm trying to figure out if this PR: [https://github.com/elastic/gosigar/pull/71/files](https://github.com/elastic/gosigar/pull/71/files)

Has been incorporated into the 6.4.3 release of Metricbeat, which is what we are using. This might help explain the discrepancy between metricbeat memory usage reports and Pingdom Server Monitor reports (which uses this code: [https://github.com/pingdomserver/server\_metrics/blob/master/lib/server\_metrics/collectors/memory.rb#L40](https://github.com/pingdomserver/server_metrics/blob/master/lib/server_metrics/collectors/memory.rb#L40))

---

<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:** [September 1, 2020, 7:32pm UTC](https://discuss.elastic.co/t/what-version-of-gosigar-does-metricbeat-6-4-3-pull-in/243757/2 "2020-09-01T19:32:05Z")

</div>

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