Ignoring a particular alarm (on purpose)?

Marc Powell marc at ena.com
Thu Feb 17 17:47:32 CET 2005



> -----Original Message-----
> From: jeff vier [mailto:boinger at tradingtechnologies.com]
> Sent: Thursday, February 17, 2005 10:44 AM
> To: Marc Powell
> Cc: nagios-users
> Subject: RE: [Nagios-users] Ignoring a particular alarm (on purpose)?
> 
> On Thu, 2005-02-17 at 10:10 -0600, Marc Powell wrote:
> > > Any idea?  (regex filter that can be passed arbitrary values via
GET
> > > variables? *fingers crossed*)
> > I don't know anything about your process for dealing with alerts but
our
> > helpdesk acknowledges alerts as tickets are created and their view
only
> > shows un-acknowledged problems --
> 
> Ah, good call.
> 
> Yes, they are acknowledged.
> 
> >
http://your.nagios.host/cgi/status.cgi?host=all&type=detail&servicestatu
> > stypes=32&hoststatustypes=3&serviceprops=42
> >
> > Using this method, they only see new problems, not ones that are
already
> > being worked. Maybe that option will work for you. There is no regex
> > filter either built in or as an addon that I am aware of.
> 
> No, that's perfect
> 
> Is there a guide to the various servicestatustypes and serviceprops
and
> such that can be passed?  (google was no help, and the code is...less
> than user friendly in this case).

Not that I've ever seen. It might be just as easy to click around
tac.cgi and status.cgi to see what's passed for the various views.

--
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_ide95&alloc_id396&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





More information about the Users mailing list