status.dat object definition

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Chris Waters
> Sent: Tuesday, March 07, 2006 12:04 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] status.dat object definition
> 
> Does anyone have a complete definition for the status.dat file?  I
need to
> know the possible values and their meanings for each part of a host or
> service object.  I have looked through the docs but I don't seem to be
> able to locate this.  I need to be able to decyper the values
associated
> with certain parts for some real-time statistics displays.  I am
looking
> for something like:
> 
> current_state= 0|1|2|3
> 0 = Host/Service OK
> 1 = Host Down
> 2 = Service Down

It's not documented at this time (for 2.0). You could use this FAQ for
the 1.x status.log as a guide. There have been a number of changes but
it's a good start --

http://www.nagios.org/faqs/viewfaq.php?faq_id=66
 
The current_state codes are the plugin exit codes --

0	OK
1	WARNING
2	CRITICAL
3	UNKNOWN	

(http://nagiosplug.sourceforge.net/developer-guidelines.html).

Everything else looks pretty straightforward or directly from the
host/service definitions. If you have any you can't figure out or it's
not clear from the source then we can help figure them out.

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
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