High swap space usage - windows swap monitoring best practice

[pioterus]

Hi,
We have Zabbix 4.4, monitoring mainly Windows servers.

Zabbix sends notes about 'High swap space usage ( less than 20% free)'. And its true of course. But the question is how to deal with this monitoring because Zabbix is to sensitive (IMHO) to this events. Pagefile on Windows when set to automatic size settings (default one) just fills up to the limits and changes to bigger sizes not so often. And that creates the problem in Zabbix and alerts admins which can do nothing (almost).

What I do is turning off automatic setting for pagefile size and set it by hand with values like: min = 1,5 x RAM, max = 4 x RAM. That of course solves the problem on one server, but there are many others. At the same time the memory usage is not so high, so it rather would not help to add more RAM. It is not Linux. Swapping on Windows behaves differently.

What is your opinion on this matter? How do you deal with swap settings on Windows servers or maybe setup Zabbix to deal with those events differently than default?

Regards
P.

[Semiadmin]

Hi, pioterus.
For a dynamic swap usage in %, you may try perf_counter[\700(_Total)\702]. If you need bytes, there are wmi.get[root\cimv2,Select CurrentUsage from Win32_PageFileUsage] and wmi.get[root\cimv2,Select AllocatedBaseSize from Win32_PageFileUsage] with custom multiplier 1048576 (1024*1024).

[pioterus]

Hi, pioterus.
For a dynamic swap usage in %, you may try perf_counter[\700(_Total)\702]. If you need bytes, there are wmi.get[root\cimv2,Select CurrentUsage from Win32_PageFileUsage] and wmi.get[root\cimv2,Select AllocatedBaseSize from Win32_PageFileUsage] with custom multiplier 1048576 (1024*1024).

But this still would give me 20% treshhold and trigger problem. Of course I can always disable trigger but not sure if it is wise. So this is basically my problem: the best scenario for Windows pagefile monitoring.