Alert confirmation

[Rob Moss]

This is a bit of an RTFM in my opinion, but here's a pointer:

Browse the list of servers in the nagios web interface.
Select your server
Select the Service, then click the "Schedule downtime for this service" 
link.

It's pretty self explanatory.

rob.

Steven Hajducko wrote:

> Is there any mechanism in nagios for a user to confirm that they have 
> seen the alert and are working on it?
>  
> The issue we have is that we come across certain disk space issues 
> that take awhile to clean up.  Because of our escalation procedure, 
> which is set in stone, the manager will get paged within 20 minutes 
> and his boss within 40.
>  
> We've discussed using enable/disable, but some people are worried that 
> alerts will be disabled and someone will forget to re-enable.  I mean, 
> after all, it's 3:15 in the morning after a 12 hour day and you just 
> deleted a bunch of files.  You're not always going to remember to 
> renable the sucker.
>  
> What we are looking for then, is something that allows me to confirm 
> that I have seen the alert and that I am working on it.  Then if the 
> state changes back to OK, to clear my confirmation of the error.  Then 
> if the issue goes off again, to alert again and need reconfirmation.  
> If no confirmation comes in within 20 minutes, then the manager gets 
> paged, 40 minutes, his boss.
>  
> Any ideas on how we would accomplish this?
>  
> --
> sh




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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