Hi,
I was wondering if there was a way to configure triggers so that the checks were performed more than 1 time before activating the trigger. As an example, if I look at the following trigger "WEB (HTTP) server is down on {HOSTNAME}", which has the following expression:
{Template_Linux:net.tcp.service[http].last(0)}=0
In the case of a failure on reaching port 80, is there a way to make sure that the check is performed 2-3 times before the trigger is activated? This is to avoid false positives in the case of network hickups. Also, is there a way to accelerate the checks during that time?
I'm curious because we're evaluating a switch from nagios and these are 2 very interesting features that we would almost certainly need.
Thanks!
I was wondering if there was a way to configure triggers so that the checks were performed more than 1 time before activating the trigger. As an example, if I look at the following trigger "WEB (HTTP) server is down on {HOSTNAME}", which has the following expression:
{Template_Linux:net.tcp.service[http].last(0)}=0
In the case of a failure on reaching port 80, is there a way to make sure that the check is performed 2-3 times before the trigger is activated? This is to avoid false positives in the case of network hickups. Also, is there a way to accelerate the checks during that time?
I'm curious because we're evaluating a switch from nagios and these are 2 very interesting features that we would almost certainly need.
Thanks!
Comment