I am currently achieving blackouts by setting up a pre-processing rule in the auto operator of the NAS with the exclude filter and all of the severity levels checked, this is where I add the hostname of the box to be blacked out. As far as scheduling the blackout, I use the scheduler with the activate profile operation to activate the preprocessing rule. To set the timing I use the recurring event mode and usually select weekly for the pattern and so on... Anyways, my problem is that if the NAS restarts when any server has an activated blackout via the pre-processing rule/scheduler, the pre-processing rule is no longer active. After extensive testing, it appears to be an issue with the scheduler and the mode "recurring event" if I use the "by time" mode instead, the pre-processing rule is unaffected and my blackout sticks through the NAS restart. My biggest concern is that all of my 100+ blackouts are scheduled using the "recurring event" mode and it is not feasible to use the "by time" mode. Does this behavior from the NAS restarting sound normal or could there be a bug here? I would appreciate any suggestions. I did notice that the pre-processing rules themselves have a "operating period" but this is limited by the hour and that is not robust enough.
You can actually get more fine-grained with operating periods than by the hour. If you double-click one of the one-hour blocks in the chart, you should get a window that pops up and lets you input a start and/or end time that does not end on an hour. If you have to do a lot of these, it might be easier to make the changes directly in the config.
Thats what I needed to find... It's gonna be a big ordeal moving them off of the scheduler and onto the operating period but it will definately help in the long run.