-
Problem report
-
Resolution: Fixed
-
Trivial
-
4.4.8
-
None
-
Sprint 64 (May 2020), Sprint 65 (Jun 2020)
-
0.25
in the memory template for "Memory utilization" the option vm.memory.size[pavailable] is used to calculate the % free memory and in preprocessing JS is used to calculate the % in use. why not just use pused instead of pavailable with JS ?
this is complicating readability of this trigger a lot
{TEMPLATE_NAME:vm.memory.size[pavailable].min(5m)} >{$MEMORY.UTIL.MAX}
as one would think that 10% free memory over 5min needs to be bigger then 90 to fire off the trigger and this makes no sence of course. So it took me some time to figure out what was the catch.
https://github.com/zabbix/zabbix/tree/master/templates/os/linux_active
also for passive