Passive Monitoring Host Checks CRITICAL

[AMacintosh]

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.

[scottwilkerson]

In you nagios.cfg you can change

Code: Select all

passive_host_checks_are_soft=1

then restart nagios

Code: Select all

service nagios restart

[AMacintosh]

Thanks. We have enabled this setting.

We are now facing an issue where the Host Check intervals are set to 5 5 5 on the remote poller but in our Nagios XI it is showing updates every 1 minute for the Host check.

ideas??

[tmcdonald]

Where are you setting the 5,5,5 for the remote host? If you are setting it in the CCM it will have no effect as the passive agents operate on their own schedule independent of any Nagios settings.

[AMacintosh]

The 5,5,5 is being set on the remote Nagios Core poller.

[tgriep]

Could you post the settings for that host check for both the local XI server and the remote server also we we can review them?