We have released version 9.0.10 of SQL Monitor which includes the ability to choose to receive notifications for only high level alerts, or only high and medium alerts (or the default of all severities) globally.
https://documentation.red-gate.com/sm9/release-notes-and-other-versions/sql-monitor-9-0-release-notes

We realise this is long overdue, as we’ve struggled to provide one solution to the different problems contained in this suggestion. As such, we’ve decided to break this down into different problems we can look to address.

We believe this release delivers the solution to the problem originally suggested, to be able to send email notifications for alerts with a Medium or High priority, so will mark this as completed.

However, please do raise new suggestions for anything you feel hasn’t been addressed by this release, so we are able to consider each one as we continue to improve SQL Monitor.

Thank you for your patience,
SQL Monitor Development Team

We are currently making improvements to the alerting, including the ability to allow multiple notification channels per severity.

We’d really like to get some feedback while it is in development, so we can make sure it meets requirements. If you’d be interested in taking a look at our prototype, please reply to sqlmonitorfeedback@red-gate.com and I’ll send further information.

Thanks
Adam

.

There is a conflict of interest inherent in alerting systems: The fewer alerts you get, you lower the notification noise, but you also lose detail in the trail of historical alerts. In many environemnts, historical alerts double as a trace of server activity. SQL Monitor users solve this by setting “Low” thresholds for things they want to see in a trace but “Medium” and “High” thresholds for the things that should trigger a notification. “Low” alerts aren’t so much alerts as they are informationlals.

We have started addressing the problem by revising our default thresholds and improving guidance in the configuration screens. Longer term, we are looking to find a better solution to the “server trace” usecase than the alerts, so that alerts can focus on their primary purpose: notifying DBAs of issues and prompting them to action.