check_ping thresholds

Michelle Murrain lists at murrain.net
Thu Nov 6 00:06:48 CET 2003


Hi Folks,

I've got everything running, and I'm learning a lot. Thanks for all of
the help. Next question:

I am monitoring some servers that are remote to me - and I'm trying to
figure out how to set the ping thresholds. 

The default setting (in the examples in services.cfg) is warning = 100.0
rta, and 20% packet loss, and for critical is 500.0 rta and 60% packet
loss. (at least this is what I think, looking at the explanations in the
check_ping config file.)

Problem is, I'm getting warning notifications at 50 rta and 0% packet
loss, and critical at 100 rta and 0% packet loss. What am I doing wrong?

I'd like the thresholds to be about what they seem to be.

Here's the service config:
define service{
        use                             generic-service         ; Name
of service template to use

        host_name                       xnet
        service_description             PING
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           5
        retry_check_interval            1
        contact_groups                  mpm
        notification_interval           240
        notification_period             24x7
        notification_options            c,r
        check_command                   check_ping!100.0,20%!500.0,60%
}

Thanks!



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list