Page 1 of 1

Notification related issues

Posted: Mon May 02, 2016 1:14 pm
by Ayush Jain
Hi Team,

I have 3 request please let me know is it possible to do it.

1.) If host is down then it will not send any notification for its services. (only for host it should send)
2.) Notification will be sent if service is showing critical since last 30 mins constantly.
3.) No notification has been sent for nagios related issues like . Return 255 out of bound error ( If nrpe is not running in host) or it should be sent only for host not all services.

If it is possible to do it, please let me know how can i do it.

Thanks,
Ayush Jain

Re: Notification related issues

Posted: Mon May 02, 2016 2:41 pm
by rkennedy
1. Yes, look into the parent / child relationships. https://assets.nagios.com/downloads/nag ... ility.html
2. Yes, navigate to Configure -> Core Config Manager -> Services (or Hosts) -> Pick a host (or service) -> Click the 'Alert Settings' tab -> Change the 'First notification delay' to 30.
3. Can you clarify what you're looking for here? I don't think it's going to be possible based on what you said.

Re: Notification related issues

Posted: Mon May 02, 2016 2:55 pm
by lmiltchev
Just to add to what rkennedy said:
1.) If host is down then it will not send any notification for its services. (only for host it should send)
If your Nagios XI server is configured properly, you shouldn't be getting service notifications when the host is down. For more information on the topic, please review the "Host And Service Check Intervals" article here:
http://sites.box293.com/nagios/guides/c ... -intervals
2.) Notification will be sent if service is showing critical since last 30 mins constantly.
As rkennedy said - "Change the 'First notification delay' to 30."
3.) No notification has been sent for nagios related issues like . Return 255 out of bound error ( If nrpe is not running in host) or it should be sent only for host not all services.
You could set up a check monitoring nrpe service (if nrpe is running as a standalone daemon) or xinetd, which is run more frequently than your other "nrpe" services on the same host. Then, set up a service dependency, so that when nrpe service is in critical state, you wouldn't be notified about the rest of the services (notification failure criteria). Read more about service dependencies here:
https://assets.nagios.com/downloads/nag ... ncies.html