Is it possible to have a check run, then IF that check fails run a different (second) check? If that second check fails then send out the notification?
For example Telnet check first, if Telnet Fails, then run a Ping check ? Just an example, we would use it for many different checks.
Escalating Nagios Checks
Re: Escalating Nagios Checks
Apart from our current escalations for notifications, we don't have a feature like that as of yet. However, we're currently developing a "Business Process Intelligence" addon that will allow services to be grouped and have AND/OR dependencies set up, which will hopefully allow for greater flexibility and more advanced options for determining a network state. So for the example below, you would group the telnet and ping, and the state would not go critical unless both were down.
We're looking at this being the first step towards a more complex rules engine for determining states and notifications.
We're looking at this being the first step towards a more complex rules engine for determining states and notifications.
Re: Escalating Nagios Checks
Excellent I think that could work for us as well. So this will be available later?mguthrie wrote:Apart from our current escalations for notifications, we don't have a feature like that as of yet. However, we're currently developing a "Business Process Intelligence" addon that will allow services to be grouped and have AND/OR dependencies set up, which will hopefully allow for greater flexibility and more advanced options for determining a network state. So for the example below, you would group the telnet and ping, and the state would not go critical unless both were down.
We're looking at this being the first step towards a more complex rules engine for determining states and notifications.
Re: Escalating Nagios Checks
Yeah, we're hoping for a 1.0 release around the end of the month. It will run on both Core and XI installs.
Re: Escalating Nagios Checks
Thankyou, looking forward to it.