Same as other people This option is really important to used efficiently our interface....
When we have some maintenance action (Backup or other scheduled) the interface sended us a lot of false alerts...
More complex rules with time or condition can be granularized into true or false alerts

I would also like to have email parsing for to be able to send to Alerts instead of to tickets.

Please add time windows for alerts too: we use bandwidth monitors on network adapters to check for bottle necks - I know that between 2am and 4am the server backups will run and near saturate the adapter, I'd like to pause the monitor during this time frame and stop the alert from being generated.

Monitoring / Alerts need to have the ability to be customized.

When you set up a monitor/alert, you should be able to set a "repeat" threshold whereas you keep getting alerts until the issue is resolved. If a server is DOWN, you get (1) alert and that's it. I would want my email blowing up like every 10 minutes when a server is down. Also, alerts need to have the ability to be put into a "maintenance mode" when doing work.

As much as an alert tells you when the server is down, you should then get an alert to let you know the server is UP. ManageEngine's Site24x7 has this feature.

When you get an alert that a server is "down" say for a windows update reboot, you get an alert after the server is UP to let you know all is well.

I'm in for more complex alerting rules creation. All alerts go to generic mailbox, but we'd like to create more alerting templates based on customers for example: we have technicians responsible for different customers, so they should get the mails. All other described features would be welcome too..

I miss a lot of options.
Events: warn if "does not contain", event types, placeholders in event sources, message contains string, performing days, number of events in xD/h/m/
Monitoring SNMP, TCP... : Number of errors in xD/h/m/, time control (hours, days of the week)

Very important for us: we would like to log entries from event viewers but it should not create an email alert.

e.g. log all critical events from server but do not create an alert to send an email (only in Atera)

Giving a use case scenario of this would be matching email alerts to specific customers to open tickets, such as environment monitoring. In our case, the emails are always sent from a generic email (which is the limited factor of the existing ticket system), but based on the contents of the email:

Customer; ABC Company
Location: My Network Room
Alert: Temp threshold exceeded

Complex rules should be able to assign that ticket directly to ABC Company.
Lots of other RMM have this ability so I feel its important for Atera to consider this