In order to check some of our APP portals from multiple locations we are implementing passive NRDP integration from CORE VMs to XI
We are still getting alerts (unknown name or service) - many of them if the parent CORE VM goes down.
- this was unexpected.
- there should be only VM down, not these multiple alerts
Notification Type: PROBLEM
Service: UK-WBR-NRDP-URL-Status-Hyperion
Host: UK-WBR-hyperion.konecranes.com
Address: UK-WBR-hyperion.konecranes.com
State: CRITICAL
Info:
Name or service not known
Date/Time: 2018-01-23 13:10:20
It doesn't make a big difference if this is an active check (configured on, and initiated from the Nagios XI server) or a passive check (configured on, and initiated from the remote box, and results then are sent to the Nagios XI server). What matters is how often the host is checked vs how often the services are checked. Do your host and it's services have the same check interval?
You will need to make host's check interval smaller than services' check interval, so that the host goes into a hard down state BEFORE services. This way, the service notifications will be suppressed. Read more on the topic here:
lmiltchev wrote:It doesn't make a big difference if this is an active check (configured on, and initiated from the Nagios XI server) or a passive check (configured on, and initiated from the remote box, and results then are sent to the Nagios XI server). What matters is how often the host is checked vs how often the services are checked. Do your host and it's services have the same check interval?
You will need to make host's check interval smaller than services' check interval, so that the host goes into a hard down state BEFORE services. This way, the service notifications will be suppressed. Read more on the topic here:
