Passive Monitoring Host Checks CRITICAL
Posted: Thu Dec 18, 2014 10:55 am
We have passive monitoring enabled using a remote poller. The problem is that passive host checks will come in as a hard state immediately. My first attempt to get around that was to create a ping check as a service and then generate alerts off of the ping check. The problem, it appears that if the host is in a hard state, then the service checks immediately become hard if they fail. Is there a way to change this behavior?
What currently happens:
Host check 1: DOWN; HARD 1
Service check 1: CRITICAL; HARD 1
Example of what we want with a service check with 3 retries:
Host check 1: DOWN; HARD 1
Service check 1: CRITICAL; SOFT 1
Service check 2: CRITICAL; SOFT 2
Service check 3: CRITICAL; HARD 3
A solution would also be to have it so that passive host checks do not always come in as CRITICAL but that seems to be the way they are setup.
What currently happens:
Host check 1: DOWN; HARD 1
Service check 1: CRITICAL; HARD 1
Example of what we want with a service check with 3 retries:
Host check 1: DOWN; HARD 1
Service check 1: CRITICAL; SOFT 1
Service check 2: CRITICAL; SOFT 2
Service check 3: CRITICAL; HARD 3
A solution would also be to have it so that passive host checks do not always come in as CRITICAL but that seems to be the way they are setup.