We run metricbeat-oss-7.9.2-windows-x86_64.zip on Windows Server 2016 and send data to Kafka. From Kafka, we consume data with Logstash and send them to ElasticCloud. We observe an issue with system.memory.swap.* metrics, which show non-zero values, although swap is completely disabled on the serve…

Metricbeat uses gosigar library, which internally runs the following code: func (self *Swap) Get() error { memoryStatusEx, err := windows.GlobalMemoryStatusEx() if err != nil { return errors.Wrap(err, "GlobalMemoryStatusEx failed") } self.Total = memoryStatusEx.TotalPageFile self.Free = mem…

@mtojek Thanks for your reply. Although it does not solve the issue we experience, it can help to fix the bug. Do you confirm this is a bug, so I can open an issue on Github?

@goodmirek5849 , we have an open issue already https://github.com/elastic/beats/issues/19875 and we are investigating other paths here, meanwhile you can use the workaround suggested in the issue.

On Windows system.memory.swap.total shows 2GB although there is no swap

Elastic Stack Beats

mtojek (Marcin Tojek) November 9, 2020, 12:16pm 4

Could you please paste any wrong reports you received? Are these random values?

Topic		Replies	Views
Odd swap metric values with Metricbeat 7.15.2 in Windows Beats windows , metricbeat	1	434	December 9, 2021
Metricbeat system.memory.actual.free - is it accurate? Beats metricbeat	3	2458	April 27, 2017
Actual memory usage on the SUSE 12 SP4 operating system is inaccurate Beats metricbeat	2	377	February 19, 2020
Metricbeat not collecting memory info Beats metricbeat	6	1384	April 24, 2017
Incorrect swap stats on Windows server Elasticsearch	1	373	July 5, 2017

On Windows system.memory.swap.total shows 2GB although there is no swap

Related topics