How to NOT fire alerts when Scheduled Downtime begins

[mocjack]

I scheduled a recurring downtime for about 100 hosts this weekend, and got a "downtimestart" and "downtimeend" alert for each of these.

Is there a way to make the scheduled downtime alerts NOT fire? We do not need to know bout this downtime as it is something that happens every week at the same time.

[mguthrie]

In the Core Config Manager, go to the Hosts/Services page->Modify->Alert Settings(tab), the "s" option under "notification options" controls notifications for scheduled downtime. Change this on your desired hosts/services, or on a common template if you're using one.

[mocjack]

Well hmmm. Is there any way to delete the pending ones en masse? There are literally 1000 on the scheduled downtime page, and it appears the only way is delete them one at a time there.

Is there a CFG file or somewhere I can more easily remove all these entries?

[mocjack]

Some more information. On the 3rd of January I scheduled what I thought was a recurring downtime for Monday mornings from 3:00AM - 4:40AM for all Windows servers.

End result is I now have showing in SCHEDULED downtimes hundreds and hundreds of downtimes for each device dating several dates into the future. There are about 780 total shown (I only have about 100 hosts!).

How can I completely kill / delete / destroy all downtimes I have previously scheduled, as obviously there is some problem with what I did or a coding issue?

I do not want downtime every night. Eventually I will want to schedule one properly for Monday mornings, but what I have now is causing missed monitoring.

Going through the list in "scheduled downtime" and deleting them one at a time takes forever... and I am not sure if they will just come back next midnight or next cycling of the Nagios server.

I just want them to all die at this point. I read one article about a downtime.dat file but I cannot locate where it is and it does not seem to be defined in the nagios.cfg file.

TIA for Anyone who can help out!

[tonyyarusso]

The downtimes are stored in the status.dat file in hostdowntime{} and servicedowntime{} blocks. I think what you want to do is write a script to issue the CGI command for cancelling them by id (an incrementing integer), and run it through whatever range your ids are.