We would also like to see an option to exclude system databases from alerting.

I would add the ability to exclude system databases from ANY of the alerts. I do not want a fragmentation alert from my msdb database for instance.

ReportServerTempDB should be excluded from the backup warning and integrity check overdue, by default.

As many SQL Instances will have the pair of SSRS DBs, these don't readily fit into the drill-down by server and instance paradigm the current UI suffers from. We should be able to invert the tree and set our alerting preferences at the database-across-all-instances level first, then override it if and when needed. This applies to ALL System Databases, of course. Taking that further, when a software vendor (such as I'm employed by) has a default deployment DB name across all customer-specific instances, the tree-inversion paradigm would also work well for our alerting configurations - they're typically the same - so an opt-in-by-User-DB to the inverted approach would be greatly appreciated.

Taking User database treatment even further - if we can assign a friendly name to a database on an instance and collect all those databases the customer wanted their name in/as, instead of the default name, again, our alerting by database first would be much more efficiently handled.

Thanks for your feedback Riken.

Thanks for your suggestion Robert.

Thanks,
Priya

The model database is almost always set to FULL, but it doesn't change much or grow. There is no reason to schedule a regular log backup.