[Nagiosplug-devel] Improved check_oracle (TS check with autoextend)

[Andreas Ericsson]

Stanley Hopcroft wrote:
>>(without that UNKNOWN thing which caused nearly a flame war here).
> 
> There are edge cases that make it less obvious whether to return UNKNOWN
> or CRITICAL.
> 
--[ snip ]---
> 
> I think that the default stance of the Nagios infrastructure handling
> plugins should be that for plugins that fail to generate output or
> return a bogus return code, Nag retuns UNKNOWN since nothing can be
> concluded about the state of the service apart from the plugin used to
> monitor it needs some examination.

It appears as though a few new return codes might be needed after all.
Suggestion for the new list;
OK = 0
WARNING = 1
CRITICAL = 2
USER_ERROR = 3 (bad arguments to plugin)
FAILURE = 4 (plugin failed to fetch threshhold data (snmp, nrpe, 
nsclient, nwstat, check_by_ssh, check_by_rsh))
NAGIOS_ERROR = 5  (internal nagios error, or return code out of bounds)

To get all alerts, a user would have to specify "w,c,u,f,e,r".

Using these, it will be much more obvious and intuitive for new 
plugin-authors to write plugins conforming to standards.
The 'UNKNOWN' state has quite deliberately been removed since it seems 
to cause confusion.

Already existing plugins should work pretty much without problems with 
the new list, but for future work it provides better flexibility.

-- 
Mvh / Regards
Sourcerer / Andreas Ericsson
OP5 AB
+46 (0)733 709032
andreas.ericsson at op5.se