-
Change Request
-
Resolution: Fixed
-
Major
-
5.0.23, 6.0.4
-
None
Current trigger expressions in filesystem monitoring templates for Windows and Linux are redundant
#5.0
{TEMPLATE_NAME:vfs.fs.size[{#FSNAME},pused].last()}>{$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} and (({TEMPLATE_NAME:vfs.fs.size[{#FSNAME},total].last()}-{TEMPLATE_NAME:vfs.fs.size[{#FSNAME},used].last()})<{$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"} or {TEMPLATE_NAME:vfs.fs.size[{#FSNAME},pused].timeleft(1h,,100)}<1d)
#6.0
last(/Linux by Zabbix agent/vfs.fs.size[{#FSNAME},pused])>{$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} and ((last(/Linux by Zabbix agent/vfs.fs.size[{#FSNAME},total])-last(/Linux by Zabbix agent/vfs.fs.size[{#FSNAME},used]))<{$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"} or timeleft(/Linux by Zabbix agent/vfs.fs.size[{#FSNAME},pused],1h,100)<1d)
We've used total-used difference instead of
vfs.fs.size[,free] usage,
so the item with the mentioned key should be added to the template, and the trigger expression should be modified accordingly to not waste CPU resources for calculating the value, which we're able to get natively.
Next - timeleft function usage - is completely redundant, which could overload the system in case of thousands of hosts monitoring. Prediction is an additional function, which should not be included by default
