Writing own plugins

[A Cline]

OK, I think I just found that on the web.

0 == OK
1 == WARNING
2 == CRITICAL
3 == UNKNOWN

I will start working on this.  Thank you very much.

Aaron


On Mon, 28 Feb 2005 16:05:52 -0600, Marc Powell <marc at ena.com> wrote:
> 
> 
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> > admin at lists.sourceforge.net] On Behalf Of A Cline
> > Sent: Monday, February 28, 2005 4:03 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] Writing own plugins
> >
> > We're writing some Windows plugins using VBscript and nrpe_nt.
> > Everything seems to work great but when the plugin goes into a
> > "Warning" or "Critical" state, Nagios doesn't seem to pick that up.  I
> > thought that nagios keyed off of the WARNING or CRITICAL or OK verbage
> > that is common in most of the output of the other plugins.  Is this
> > correct or is there some other mechanism that nagios uses to determine
> > if things are in a Warning or Critical state?
> >
> 
> Nagios only looks at the exit code of the program to determine state.
> 
> http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN75
> 
> --
> Marc
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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