Really dumb question - how do folks distinguish unreachable from over threshold ?

Chet Luther chet.luther at gmail.com
Thu Jul 6 14:58:12 CEST 2006


On 7/5/06, Stanley.Hopcroft at dest.gov.au <Stanley.Hopcroft at dest.gov.au> wrote:
> Is it possible to use the standard plugin distro check_ping to
> distinguish
> a reachability failure brought about by sluggish transport and one
> caused
> by a routing failure.

The easy answer would be to setup your host checks using a check_ping
setting that is very tolerant to latency and packet loss.  Then setup
a service that uses check_ping with your acceptable latency/packet
loss.  You could then use this service in a service dependency for
troublesome services behind the router if you intended to suppress
notifications.

You could potentially use something like <a
href="http://oss.oetiker.ch/smokeping/">SmokePing</a> for the service
check if you were interested in fine-grained latency/packet loss
information.

-- 
Chet Luther
chet.luther at gmail.com

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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