When you run an upgrade, there should be an option that just uses the current service credentials (i.e. leaves everything as is) instead of having to re-enter them.

Allow the use of managed service accounts (MSA and gMSA) as credentials when monitoring servers.

Given the high-level permissions required to fully monitor servers, this would provide a higher level of security to match.

It would be really useful is this feature came into Live!

We have a number of queries that run on our SQL servers. We are aware these normally run for a long period of time (5-10 minutes) and do not want to exclude these from being alerted to us. Rather than changing the Long Running Query threshold for all the queries within the server we would like to be able to do it for these specific queries that take that little bit longer than others.

When a cluster spans regions I want to be able to only monitor my "active" region and note my "passive/DR" region.

If my primary region fails I would like to switch over my licenses to the other region in SQL Monitor so that I retain my license count.

It would be great if SQL Monitor could invoke a SQL script upon an alert threshold being crossed and then take action within itself (ie. clear itself, notify a team, etc) based on the value returned (0/1) or default to an action if there is an issue with the script execution.

This type of functionality would help administrators have a first line of defense before truly getting paged on an alert such as a drive filling (perhaps you have txt files you can purge or shrink logs (though I don't necessarily condone this, but you get the idea!)

I would like to be able to exclude specific queries from Top 10 Queries. We use SQLQueryNotificationService which means our top 10 queries based on duration are always showing these queries as they have a waitfor. I would like the ability to exclude items from the top 10 queries.

Typical query I would like to able to exclude:
WAITFOR(RECEIVE TOP (1) message_type_name, conversation_handle, cast(message_body AS XML) as message_body from [SqlQueryNotificationService-07e6439b-8276-45aa-963f-bed011b3ef2f]), TIMEOUT @p2

check if there are any service packs or updates for my SQL Server instances. This could then raise an alert to prompt me to investigate these updates.

During a monthly patch round along the servers, a restart or some downtime is mandatory. I want to be able to select the actions SQL Monitor will perform with the alerts triggered within that maintenance window. Most of the time I'm aware of the required Windows reboot, so I do not need an email telling me that the SQL Server was not reachable for a short period. So I would like to tell SQL Monitor not to trigger any alert during the maintenance window. (preferably a one-time maintenance window, see other suggestion)

We use SQL monitor very heavily for our SQL and application monitoring, what we would like is for each alert to be able to define a custom sql script to run when the alert is raised, the output of this sql should be included in the alert.

This would allow us to do things like capture whoisactive when blocking occurs or other application specific things and make responding to alerts MUCH easier.

I have two failover clusters in Azure using ClusterSharedVolume storage, migrated from terrestrial clusters.
I've been using SQL Monitor to monitor all aspects of these clusters but now I've migrated to Azure, the monitor can't connect (I believe it's to do with the inability to ping the cluster load balancer in Azure).
I'm sure, as more and more of us migrate to cloud services, that covering an Azure cluster would be most welcome.

The nag about "you haven't set up any maintenance windows" is something you could allow us to turn off. Period.

SQL Monitor's simplistic feature does not tie in with the way Rackspace performs their patching, so the feature is useless and the nag is annoying as it keeps on coming up and we keep on dismissing it.

Please, give us a "Turn of maintenance window reminders globally" option - it can't be that hard to do...

Present the detailed Step error message for Agent Job Failures. Currently shows the Job message, but not the error from the step that actually failed. This requires the user to open SSMS and drill down to find what caused the failure, instead of getting a head start from SQL Monitor.

Please make a mobile app for iphone / ipad like SQL Sentry do!

it would be nice if we could export selected alerts (for instance full deadlocks related information) to forward to our "partner" so they can analyse the problem.

While the alert for blocking process is great, it would be nice to be able to configure the trigger for number of descendants affected as well.

If a blocking process runs for 30 seconds and affects 10 people but the alert is configured for a one minute duration of the block it would obviously not let you know

When I define a custom metric it would be super-helpful to be able to see some details that gave rise to the metric value. For example, I have one for "count of failed SQL logins in the last 10 mins". But to find out which logins failed, I have to go run queries in SSMS.

I'd like to be able to define a "details" query on the custom metric, the results of which are captured at time of collection, and are then available from the alert.