The only thing I see implemented is the option to pause alerts on multiple servers at once which is an improvement, but like a reaction below, since you can only pause for 5 hours max, this still isn't what I and others are looking for.

The way the implementation would make more sense if it was a checkmark in an automation profile, and by selecting that checkmark Atera would disable the alerts on all machines impacted by that profile as long as the profile is running.
So if I would schedule an windows update run in the weekend starting at 10pm, as of that moment all machines that are being updated by that profile should be paused untill the update run has finished.

I just got the email saying that this feature was implemented but it looks like you're only able to pause the alerts manually.

As the title of the feature request mentions a patching window is normally a regularly scheduled window of time in which patches take place.

If our business *always* updates our servers at 12 AM on the last Friday of every month, we should be able to schedule Atera to pause alerts during this time every month without having to manually go in and pause alerts for servers every time.

The only thing the change that Atera made that seems to be a time saver here is the ability to automatically resume alerts after a set amount of hours.

We could already manually disable alerts on a server if we wanted to but after today we would no longer need to remember to resume alerts.

Also the default number of hours you can pause alerts for doesn't really make sense.

Say I leave work at 5 PM, with the feature as it is right now I can only pause alerts for 5 hours. So our server's scheduled patching would have to take place between 5 PM and 10 PM and we couldn't schedule it for later in the night.

This becomes more of a problem when managing servers from different timezones. If I work in Eastern time and I also manage servers in Pacific time, our scheduled server maintenance would need to take place at 7 PM Pacific time at the latest if I left work at 5 PM Eastern.

It's not logical when triggering a reboot during execution of an Automation Profile from Atera system that an alert is generated

We need a weekly maintenance window, since we reboot our servers to apply windows updates every week on Saturday at 1 am. Thank you.

It would be great to have an maintenance mode for service updates!

We need a patching automated schedule like mentioned by others. We also have tons of alerts because some servers are shutdown after hours to save Cloud compute costs (ex: Some Dev/QA Environments). We know these don't need to be monitored during that maintenance window, so we would like to be able to schedule this. Avoid Red Alerts for nothing in the dashboard.

yes, such a small change would help enormously!

This would be a great feature

I like the idea of a note comment field to attach to the alert 'override'.

This is a key feature for me, to be able to simply add a time in hours that I type in, instead of the choice of a few pre-set buttons.

We may be waiting for parts or field tech to get out to an alerting configuration item. I might be weeks. I need to be able to just put that item on ignore for extended amounts of time without change group, etc. (could be months. ~720 hours per month, ~8,640 hours per year)

We just had a planned power outage at 2 sites.

I feel it is a major oversite by the Atera Team to not have scheduled (known) maintenance periods to pause alerts.

Looking at the comments that this has been requested and under review for nearly a year, I am disappointed.

When doing maintenance of whatever on multiple machines, it would be very handy to pause the alerts on all those machines in one time. Now you can only do it per machine.
There is already a multiple select for machines when you're looking at the machines of a customer, so adding a button to pause alerts shouldn't be that difficult I hope.

Just did the first windows update run using Atera this weekend, and this caused around 600 emails with warnings from cpu, availability etc.
This feature is really needed, mailfloods like this are unwanted.

This is something I have requested of Atera as well. Additionally, just a bulk pause feature would appreciated as well. We do maintenance frequently on several servers at once, so getting several alerts coming in during a maintenance windows becomes frustrating when you have to pause alerts for each device individually.

Yes a Maintenance window with pause alerts would be very helpful, also it would be nice to be able to select multiple devices on the devices page and pause alerts for all at once.

We wanted to migrate our server monitoring and management from N-ABLE RMM to Atera. But as we found out that we cannot schedule maintenance windows, we stopped the migration.
We are monitoring services with a script in case of an alert, but this script must not run in the maintenance window as this service has to be and stay stopped.
Scheduling maintenance windows is a must have!

This is critical to us as well

Additionally, we need the option to add a comment why it is paused (e.g. not connected to switch, temporary down until replacement). The comment needs to be seen clearly so that everyone in the team is informed about the pause

Currently, you can pause alerts from the Device > Manage > Pause Alerts for up to 5 hours, we have a server we won't reach for over two days so we need a longer option

More than three quarters of our tickets are from update restarts. This is ridiculous. How is it still not fixed?