Yes I agree...
But, I do export to a third application the service's perfdata. (using
service_perfdata_file* instructions of Nagios).
That third application is extracting from it whether services are up or down
and doing some actions in consequence.
This behavior is a problem to me because of two
On Feb 18, 2010, at 3:47 AM, Samuel Bancal wrote:
> Thanks for your answer,
>
> In fact it is normal behavior to me also.
> Thing that is not "normal behavior" to me is that between two checks, Nagios
> jumps from "SOFT 1" to "HARD 1" without doing the steps "SOFT 1" > "SOFT 2" >
> "SOFT 3" an
Thanks for your answer,
In fact it is normal behavior to me also.
Thing that is not "normal behavior" to me is that between two checks, Nagios
jumps from "SOFT 1" to "HARD 1" without doing the steps "SOFT 1" > "SOFT 2"
> "SOFT 3" and finally "HARD 4".
Regards,
Samuel Bancal
2010/2/17 Morris, Pat
Samuel Bancal wrote:
> Nagios Core 3.2.0
> nagios-plugins-1.4.14
> Ubuntu server 8.04.3 LTS
>
> Hi,
>
> I'm encountering problems to configure the notifications in case a
> server is no more responding to PING (ICMP).
> I don't understand why Nagios is jumping over steps when it's doing
> service
Nagios Core 3.2.0
nagios-plugins-1.4.14
Ubuntu server 8.04.3 LTS
Hi,
I'm encountering problems to configure the notifications in case a server is
no more responding to PING (ICMP).
I don't understand why Nagios is jumping over steps when it's doing
service-check "icmp".
Here is the config :
defi
