[Nagiosplug-devel] Working on testcases
John P. Rouillard
rouilj at cs.umb.edu
Fri Nov 4 10:01:25 CET 2005
In message <08AB1E2F-6783-47ED-B15C-BDD745DB345B at altinity.com>,
Ton Voon writes:
>My "bad" scenario:
>
> - Nagios configured to alert on critical/warning - but not unknown
>- for a check_http on wiki.internal.company.com
> - Nagios also configured for critical on check_dns to check
>nameserver, but not specific wiki.internal.company.com record
> - Someone deletes the DNS entry for wiki.internal.company.com by
>mistake
> - Nagios says check_dns is okay (nameserver still running)
> - check_http on wiki.internal.company.com returns UNKNOWN because
>cannot resolve hostname
> - however, no alert. Sys admin gets b0ll0cked for not spotting
>problem :(
>
>Three ways to fix at the configuration level:
> - check_http against IP address, but then removes point of DNS
> - alert on unknown, but then what's the point of unknown?
> - for each hostname used, configure a check_dns for it. But that
>sounds like a huge (and unobvious) overhead
How about a flag to set the exit status in case of a failed lookup?
>Am I worrying too much?
No, I don't think so.
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
More information about the Devel
mailing list