Nagios and exception monitoring

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Scott Micciche
> Sent: Tuesday, January 30, 2007 4:05 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios and exception monitoring
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Is there any way to configure Nagios to only show the exceptions on
the
> service detail and associated pages?

Sort of...  You can manipulate the filters to show subsets of problem
types. For example, the following will show all un-acknowledged service
problems in WARNING or CRITICAL state. We use this as our default
Service Problems link --

http://you-nagios-host/cgi-bin/status.cgi?host=all&type=detail&servicest
atustypes=20&hoststatustypes=3&serviceprops=42

servicestatustypes -- 4 (WARNING) + 16 (CRITICAL) = 20
	2 == OK
	4 == WARNING
	8 == UNKNOWN
	16 == CRITICAL

Hoststatustypes -- 1 (Pending) + 2 (UP) = 3
	1 == Pending
	2 == UP
	4 == DOWN
	8 == UNREACHABLE
	
Serviceprops and hostprops can be found around line 272 of
include/cgiutils.h (too many for me to write here). For the example
above, 42 means "Not In Scheduled Downtime & Has Not Been Acknowledged &
Active Checks Enabled"

Many of the interesting combinations can be reached just by following
links on the Tactical Overview.

--
Marc

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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