Multiple triggers broken. (1.4.x, 1.5.x)
I'm finally getting around to posting this problem. I have verified this problem to exist in both 1.4.x and 1.5.3.
I have setup a trigger which looks at the min and max value of the host:status item over a specified period of time. The first trigger should go off after 5 minutes, and it does. The second should go off after 10 minutes, but it does not, it goes off at the same time as the first. The two tier triggering is an attempt to work around the lack of escalation. The first trigger is a severity of HIGH, the second DISASTER.
Trigger 1:
Name: Server {HOSTNAME} is not responding
Trigger 2:
Name: Server {HOSTNAME} is unreachable
First off, I will ask the obvious, am I doing something wrong?
Second, can anyone else verify?
I have setup a trigger which looks at the min and max value of the host:status item over a specified period of time. The first trigger should go off after 5 minutes, and it does. The second should go off after 10 minutes, but it does not, it goes off at the same time as the first. The two tier triggering is an attempt to work around the lack of escalation. The first trigger is a severity of HIGH, the second DISASTER.
Trigger 1:
Name: Server {HOSTNAME} is not responding
Code:
({Template_Linux:status.max(300)}=2)&({Template_Linux:status.min(300)}=2)
Name: Server {HOSTNAME} is unreachable
Code:
({Template_Linux:status.max(600)}=2)&({Template_Linux:status.min(600)}=2)
Second, can anyone else verify?