> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Andrew Cruse > Sent: Wednesday, September 26, 2007 12:58 PM > To: [email protected] > Subject: [Nagios-users] Status.cgi question > > I can't believe this isn't in the documentation so I fear I'm looking the > wrong place, but I sure can't find it. I'm playing with the output of > status.cgi like this: > > http://nagioshost.domain.com/nagios/cgi- > bin/status.cgi?host=all&servicestatu > stypes=248 > > And I'm trying to figure out what the various options are for host and > servicestatustypes. What I'm trying to do is display a window which shows > all service problems (unknown, warning, and critical) that haven't been > acknowledged. That's easy except for the acknolwedgement part. The best > I've been able to do so far is display all service problems *including* > those that have been acknowledged. Is there any way to exclude > acknowledged > problems?
We use -- status.cgi?host=all&type=detail&servicestatustypes=28&hoststatustypes=14 &serviceprops=42 >From include/statusdata.h, servicestatustypes is the sum of -- #define SERVICE_WARNING 4 #define SERVICE_UNKNOWN 8 #define SERVICE_CRITICAL 16 hoststatustypes is the sum of -- #define HOST_UP 2 #define HOST_DOWN 4 #define HOST_UNREACHABLE 8 (we _really_ use 2 here since all our hosts appear up all the time) >From include/cgiutils.h, serviceprops is the sum of #define SERVICE_NO_SCHEDULED_DOWNTIME 2 #define SERVICE_STATE_UNACKNOWLEDGED 8 #define SERVICE_CHECKS_ENABLED 32 HTH, -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
