[Nagiosplug-devel] Nagios::Plugin api

[Ton Voon]

On 30 Aug 2006, at 21:04, Vonnahme, Nathan wrote:

> I like that, it is more intuitive.  Maybe it should default to UNKNOWN
> though-- you should explicitly throw CRITICAL or WARNING if it's an
> expected problem (the thing you're checking is down/excessive), and  
> just
> plain die() (which would return UNKNOWN) if it's something that keeps
> you from checking, like if a file your check script needs isn't there.

Agreed. UNKNOWN is a better default.

> What about even overloading the die and end handlers like this (I may
> not have it quite right... and you'd have to do it in the check  
> script,
> not the module) ?

I like the idea of overloading die - keeps it v simple - but only if  
it doesn't need to be specified at the plugin script (eg, can we get  
it automatically just by use Nagios::Plugin?).

Also, does that mean the object will return the data? Or all the  
setup stuff is class data?

Ton

http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-plugins.org/archive/devel/attachments/20060831/e1e7a09f/attachment.html>