Page 1 of 1

schedule downtime for multiple hosts AND their services

Posted: Wed Nov 19, 2014 7:23 am
by MichielvM
Hi,

I was looking for an easy way to schedule a downtime for a group of hosts including services.
Stumbled upon this thread: http://support.nagios.com/forum/viewtop ... 7&p=101620
Can't comment on it because it has been locked down.

I'd like to know if a feature request was entered to develop a method limiting the actions to achieve this.

As I understand from that topic I need to schedule a hostgroup downtime AND another one for services.
I'm sure that many admins on this board will appreciate this, as maintenance windows are perty common.

What I would like to see:
- a presented list of available hosts to add (like the selection procedure in bulk modification)
and the option to select a hostgroup as it can be handy too.
- check box to include all services

And it would be nice to present this function in the Incident Management section of XI sidebar.
Would make life so much easier.

For now I'll just go with the tedious task of creating a temporary hostgroup, adding hosts and creating 2 schedules.

Re: schedule downtime for multiple hosts AND their services

Posted: Wed Nov 19, 2014 9:25 am
by snapon_admin
Personally, I'd rather not have checks ran during scheduled downtime at all. Why would I want to see thousands of critical statuses for hosts and services that I already know are going to be broken because the server is in maintenance. I think I put in a feature request for a "Disable active checks during downtime" check box type of option. Can't recall if I actually did or if I just meant to though. I'm also not sure if I'm the only one who would actually want that or not. Just my .02.

Re: schedule downtime for multiple hosts AND their services

Posted: Wed Nov 19, 2014 12:17 pm
by MichielvM
Well, the sole purpose of a downtime schedule is to avoid bogus alerts during maintenance.
:)

Re: schedule downtime for multiple hosts AND their services

Posted: Wed Nov 19, 2014 4:17 pm
by lmiltchev
I've added an internal feature request about an year ago (TASK ID 1035). It hasn't been acted upon yet. Feature requests have lower priority than bug fixes so it may take some time before this is (if ever) implemented.