[Nagiosplug-devel] r1879: check_tcp now returns UNKNOWN with an invalid hostname on command line

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/01/08 08:39 AM, Ton Voon wrote:
> On 8 Jan 2008, at 12:27, Thomas Guyot-Sionnest wrote:
>> I don't believe this should apply for plugin that use a protocol to
>> check something behind it (i.e. check_snmp, check_nrpe, check_by_ssh,
>> check_nt). It that case this should be UNKNOWN with optionally the
>> possibility to return CRITICAL on protocol unreachable. So instead of
>> setting 10 thousand dependencies in Nagios you can just have one check
>> for the protocol (using the CRITICAL option or negate) and all other
>> returning UNKNOWN when unreachable - this ways you won't get a "pager
>> bomb" then the service does down ;)
> 
> It means that you have to have at least 1 other check of the protocol  
> setup in Nagios, which is not always the case. I personally agree with  
> this, but not sure if it should be in the guidelines.

Well, otherwise the guidelines would specifically forbid these plugins
from returning UNKNOWN. If you take check_nrpe for example, not being
able to reach the host doesn't mean the plug-in would fail, and having
many nrpe check would cause many alerts if a single component, nrpe, fails.

Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHg4V96dZ+Kt5BchYRAtrJAJwO1Rj2F/epju8k/Cspbtr8l1gjWgCcD75G
wSWTrjDY49p616g5UD3bIAw=
=FdC1
-----END PGP SIGNATURE-----