Quoting Edward Morbius <dredmorb...@gmail.com>:
>
> When some things are going well and others aren't fully up to speed (slow
> database), we'll get a "DATABASE_TEST_RAN_LONG", which isn't ideal, but at
> least for a few occurances (n <= 5) we can live with. In particular, we
> DON'T want a single result sounding off pagers in the middle of the night.
You can specify -e "OK,DATABASE_TEST_RAN_LONG", then let the plugin decide if
it's slow or not, with the -w, -c and -t parameters.
Terry
[-w <warn time>] [-c <critical time>] [-t <timeout>] [
>
> The current test looks like:
>
> define command{
> command_name check_jetty
> command_line /usr/lib/nagios/plugins/check_http -H
> '$HOSTADDRESS$' -u /serviceStatus -e 200 -s OK
> }
>
> What would be a sane process of getting Nagios to:
>
> - Report all clear when we get a 200 status and "OK" text on page?
> - Wait for 6 consecutive instances of "DATABASE_TEST_RAN_LONG" before
> alerting for that result.
> - Alert immediately on any cases not matching one of the above?
>
> I don't believe we can capture this in a single test unless I'm missing
> something.
>
> Thanks in advance.
>
> --
> Dr. Ed Morbius
> Chief Scientist
> Krell Power Systems Unlimited
>
--
Terry Carmen
CNY Support, LLC
Web. Database. Business.
http://www.cnysupport.com------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users@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
