Host and Service Alerting/Scheduled downtime

[drakeu]

I actually have two questions, somewhat related.

1) In Nagios Core, I recall in the web interface you could click something similar to "Disable all service notifications" and there was also a check box for something like "Disable host notifications also". I do not see that in NagiosXI. Right now, the only way I can see to accomplish this is to click on each service under the host individually and select "Disable Notifications". Am I missing something or going about this incorrectly?

2) I've found when scheduling downtime for a host, after it comes back up, it will still notify on individual services that are down, even though the host is scheduled for maintenance. Here is an example:

We have 1 host that is rebooted and backed up with its services stopped every night at 3am. We are also monitoring several services, including http, on this host. At 3 am the server reboots. The host down notification is suppressed because we have scheduled downtime from 3-4am. However, once the server comes back up from the reboot, at 3:10am, it begins checking the http service and alerting that it is down. (The http service is not restarted until about 3:45am via a scheduled job). To address this I have scheduled downtime for the host AND for the http service from 3-4am. This works, but would be a real issue on some servers where there were a lot of services. Is it possible to schedule downtime for all hosts AND services on that host at once? In other words, what I'm hoping for is, I could schedule maintenance for the host from 3-4am and it would suppress notifications for host down AND service down. What I'm expecting when I schedule maintenance for a host that Nagios would recognize that the services may also be down during maintenance and suppress all alerts. Is this, or will this be possible?

Thanks!

[mmestnik]

Yes.

Yes.

You can still access this via the core interface as you used to. I'm not sure if it's anything that will be integrated into XI.

This is by design. You will have to either make the host go down so that the "is reachable" check fails or apply your downtime to the service effected. Service dependencies help here.

If you have things configured correctly and you are only taking down one service you should be able to put that service into downtime and the rest of the things that alert should be under that umbrella. If you plan to take down a whole lot of things, then it stands to reason that setting up a lot of downtimes would be part of that.