Hi
Using zabbix 2.4.2 on Client and Server (upgraded from a beta of 2.0)
For some issues zabbix never takes the issue out of "PROBLEM" status even when the trigger condition is no longer triggered. This happens for CPU and entropy. For entropy I switched the trigger and that might have solved it but for CPU I tried a couple of options neither worked:
{gss:system.cpu.load[all,avg5].min(10)}>8
{gss:system.cpu.load[all,avg5].last(0)}>8
{gss:system.cpu.load[,avg5].last(3)}>8
I also upped the start pollers at one point because zabbix was 100% busy...
Using zabbix 2.4.2 on Client and Server (upgraded from a beta of 2.0)
For some issues zabbix never takes the issue out of "PROBLEM" status even when the trigger condition is no longer triggered. This happens for CPU and entropy. For entropy I switched the trigger and that might have solved it but for CPU I tried a couple of options neither worked:
{gss:system.cpu.load[all,avg5].min(10)}>8
{gss:system.cpu.load[all,avg5].last(0)}>8
{gss:system.cpu.load[,avg5].last(3)}>8
I also upped the start pollers at one point because zabbix was 100% busy...



Comment