Hello,
I have an issue which, I guess, other people have encountered, but I can't seem to find a solution for. The situation is like this: NagiosXI 5.4.13. Traffic going through a lot of unstable tunnels. A lot of SNMP queries timing out(which is expected due to the tunnels' instability). When I have a device with a critical state(for instance service "httpd" is down) a notification for critical comes. After that the connection becomes lousy and I get Unknown notification, after that the connection becomes good again and I get Critical notification. I can deal with the Unknown notifications by simply configuring notification settings, but then I just receive critical notifications every time the quality of the tunnels is restored. I cannot use flapping control, because the time interval between tunnel degradation differs between 5 min and 4 hours.
So my question is - does anyone have a suggestion how to stop sending notifications, when jumping from Unknown to Critical(or Warning for that matter)?
Cheers.
Critical-unknown-critical state change notifications flood
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Critical-unknown-critical state change notifications flo
I'll leave this open for others to chime in, but the only solution that makes sense to me is resolving the problem that causes the VPN to degrade
Re: Critical-unknown-critical state change notifications flo
Unfortunately the tunnels are between continents and stability cannot be fixed. This is why I am looking to eliminate, or at least reduce the spam.
Is there a way to make Nagios think that Unknown status is actually OK status regarding notifications(I guess expecting one master "switch-case" where I can set OK and Unknown in the same case is naive, but perhaps by editing a couple of config files this can be done)?
Is there a way to make Nagios think that Unknown status is actually OK status regarding notifications(I guess expecting one master "switch-case" where I can set OK and Unknown in the same case is naive, but perhaps by editing a couple of config files this can be done)?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Critical-unknown-critical state change notifications flo
In the nagios.cfg there is this configuration
If you set it to
and restart nagios
It will mark ALL checks that timeout as OK
This is the only thing I can think of but it will affect ALL checks
Code: Select all
service_check_timeout_state=uCode: Select all
service_check_timeout_state=oIt will mark ALL checks that timeout as OK
This is the only thing I can think of but it will affect ALL checks
Re: Critical-unknown-critical state change notifications flo
Thanks, not what I was really looking for, but I will see if I can make it work somehow.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Critical-unknown-critical state change notifications flo
Sounds good!gnikolov wrote:Thanks, not what I was really looking for, but I will see if I can make it work somehow.