Further differentiating between Acknowledged and Un-acknowledged problems

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Friedrich Clausen
> Sent: Friday, June 23, 2006 9:38 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Further differentiating between Acknowledged
and
> Un-acknowledged problems
> 
> Hi,
> 
> I hope my subject is not confusing. A little background first - We
have
> a NOC that monitors that status of various devices and services,
through
> the "service problems" section of the CGI.
> 
> I received a request to make acknowledged problems "go away" from the
> "service problems" section. I only way to could see to do this is to
> modify the CGI's. So there could be couple of side navigation bar link
> changes, eg. "All Service Problems", "Unacknowledged Service Problems"
> and "Acknowledged Service Problems".

This is exactly our workflow and no source modifications are needed.
It's just a matter of constructing a URL that has the necessary flags.

You can go to the tactical overview and click on the 'xx Unhandled
Problems' link to only show unhandled problems. To show both Unhandled
Critical and Warning Service issues you could use a link like the
following that combines both views --

http://your-nagios-host/nagios/cgi-bin/status.cgi?host=all&type=detail&s
ervicestatustypes=20&hoststatustypes=3&serviceprops=42

--
Marc



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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