That is one solution for the problem. Unfortunately for us, we have many Windows servers and leave their pagefile (swap space) to be managed by Windows.
When Windows manages the pagefile, it leaves the pagefile size alone even sometimes filled with 0 bytes free until some program requests more memory and then if it has space on the pagefile drive, it will grow the size of the pagefile providing more free pagefile space.
This confuses the "simple" Zabbix alarm. It sees, for example, a 1.7GB page file with 0 bytes free and throws an alarm. It didn't see that Windows was managing the pagefile and the drive had plenty of disk space available for pagefile growth.
It'd be great if Zabbix could (psuedo code follows):
IF "Windows is managing the pagefile" THEN
IF
pagefile free space % is lower than threshold
AND
drive containing pagefile has less free space than 2nd threshold
THEN
throw trigger (send alarm)
ELSE #assumes fixed pagefile size on a drive
IF
pagefile free space % is lower than threshold
THEN
throw trigger (send alarm)
FI
This trigger complexity is beyond my Zabbix skill rating.
If anyone has suggestions on how to implement this it would greatly help.
(We chase 4 to 5 production level swap space alarms each day. Correction, ignore. Which scares us and should scare Zabbix developers. Crying wolf is not a good thing.)
Bill