Suggestions
Welcome to the Redgate Monitor feature suggestions list. Tell us how we can improve Redgate Monitor by voting on these suggestions or by submitting your own ideas.
This is the easiest way to make an impact on Redgate Monitor’s roadmap. Check out the completed suggestions to see how your ideas have influenced us in the past. Please note that this list is one of multiple sources that drive our development, meaning that we will not always implement the highest-ranking suggestions.
To give your idea the greatest possible impact, please follow these guidelines:
- Describe the goal you’re trying to accomplish, rather than a specific solution to get there
- If you have a favoured solution, add it as a comment to your suggestion
- Give us as much context as possible
- Only make one suggestion per post. If you have multiple ideas, submit them in separate posts
- Comment and vote on existing posts to develop the ideas — the Redgate Monitor team will often stay quiet initially about new suggestions to see what you have to say!
If you have any questions visit the Redgate Monitor forum.
228 results found
-
filter webhook notifications
I would like to be able to filter which webhook notifications get sent out via an option in alert settings - notifications.
e.g. for each alert, we have the option to send an email to a default address, an alternative address, or don't send an email for this alert.1 voteAs of SQL Monitor 11.1.8 Webhook notifications can be enabled and disabled for an alert type within alert settings (see screenshot).
-
Azure ad intergration
My wish is that my users can sign-in with azure user account.
19 votesThis can be achieved by using OpenID Connect authentication with Azure Active Directory. See https://documentation.red-gate.com/sm/adding-sql-monitor-users/authenticating-with-openid-connect and https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/auth-oidc for more information.
-
Have the option to capture parameters from queries
Presumably this would require having the trace enabled and you wouldn't necessarily want to be capturing every parameter on every query so there probably needs to be some logic around choosing what to keep. This would obviously help track down parameter sniffing problems along with other troubleshooting of the exact scenario you are trying to look at.
This is different from the suggestion listed here:
https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/41237467-display-parameter-list-in-the-query-plan-form(And that one should also be implemented and would be a valuable time saver)
8 votesPreview support for monitoring individual query executions for user selected SQL Servers was introduced in version 14.0.39 (January 8, 2025).
When enabled on an instance, data such as start and end times, duration, reads and writes, and query text can now be viewed and parameters appear in the query text.
-
Be able to identify Base Monitors by a user friendly name in a MSP Solution
For example in the "Manage Servers" screen, when using a MSP Solution, it's only possible to view the actual names entered on the Base Monitor Configuration page.
Without having to resort to a DNS work-around for this issue, it would be nice to add the option to use a "Display Friendly name" instead of the name of the Base Monitor Server.
That way, people who don't know which individual server belongs to which individual client or base monitor, can easily identify them based on their displayname.2 votesThis is now possible from version 11.0.4
-
Webhook notifications need to be configurable at an alert level
While Webhook notifications is a cute idea, it has no value to me if I can't customize what alerts get it. Please add a Webhooks column to the individual alert settings.
20 votesAs of SQL Monitor 11.1.8 Webhook notifications can now be enabled and disabled for alert types.
This can be done within the alert settings page for each alert type (see screenshot).
-
Recognize Low Alerts visually in overview
Low Alerts show as blue dots on the Latest Alerts panel, but in the overview they show Green like Healthy.
Especially when showing Small Tiles (we monitor 60+ instances) they do not stand out from Healty ones (see the attached examples).For that reason I dont use many Low Alerts.
It would be more consistent to use blue in the overviews also.4 votes -
search Top Queries
I have a process that reports on stored proc outliers. When I go to SQL Monitor, it is very difficult to search the top queries to find the particular stored proc.
For instance, if I do a ctrl+f and search for "I.Invoices", the search may find that snippet in "hidden" areas (in the dropdowns) but I cannot tell where the found items are.
A query syntax search of the top queries would be extremely helpful.
9 votesQueries can now be searched. This is available from version 11.2.10.
Query search is still in preview. Please send any feedback to SQLMonitorFeedback@red-gate.com.
-
SQL Monitor Audit Trail
It would be nice to have an audit trail of changes in SQL Monitor. For example, if an alert is changed, a new instances is added/removed, or users are added or removed.
26 votesStarting with version 14.0.57 (released on May 6, 2025), the Enterprise Edition of Redgate Monitor includes an audit log of user activity in Redgate Monitor, capturing sensitive changes such as modifications to alert settings. and the addition or removal of users and monitored instances
-
Job Duration Unusual: Threshold higher than 100%
Currently when configuring different threshold in the "Job Duration Unusual" alert we are limited to a maximum of 100% of the baseline. So for example if I wanted an High alert when a job is 5 times the baseline it's not currently possible, I'm limited to 2x.
7 votesAs of version 10.0.9, it is possible to enter thresholds over 100% for the job duration unusual alert.
-
Show Job name instead of ID in query related alerts
This is a follow-up on: https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/1865305-show-job-name-not-job-id-value-for-job-related-ale
The job ID was replaced by the job name in Job Failing, Job Duration, Job Cancelled alerts but I would like to see the same for query related alerts, specifically Long-Running query but the comments in the other item also mention Block Process and Deadlocks.
12 votesThis is available in v 13.0.54.
-
See on the overview page incase of a AlwaysOn or a windows cluster which node is the active\primary
We have several windows clusters and AlwaysOn clusters. It would be very helpful to see on the overview page which node is active.
It can be easily done by adding a color to the AG icon on the tile.
I know that it can be seen on the cluster overview but I really think it belongs on the Overview page.
29 votes -
Ability To Alias PaaS (SQL Azure) Instances
You currently can alias IaaS instances but the option does not show up if it is a PaaS instance.
8 votesThis has been added now. Please let us know if you have any further feedback about this at SQLMonitorFeedback@red-gate.com
-
Suport for Azure SQL Hyperscale
Add support for the new Azure SQL Hyperscale PaaS solution
120 votesRedgate Monitor supports monitoring Azure SQL Database running on the Hyperscale service tier.
Both the primary and replicas can be monitored in a similar way. More information is available in the documentation: https://documentation.red-gate.com/monitor/azure-sql-database-hyperscale-313492584.html
-
Monitor Azure Managed Instances
Redgate Monitor still does not appear to fully support Azure Managed Instances. As our primary business is about to move across solely to Azure Managed Instances, this is now a seriously high priority for us.
We are heavy users of Redgate Monitor for our business, so this is now starting to be become a bit of a worry for us.
46 votesWe're now supporting Azure Managed Instances.
If there is something you think we're missing from this feature, please let us know at SQLMonitorFeedback@red-gate.com
-
Wire up Notifications to MS Teams (in addition to Slack)
Wire up Notifications to MS Teams (in addition to Slack)
12 votesNotifications can be sent to Microsoft Teams using Webhook notifications. See https://documentation.red-gate.com/sm/metrics-alerts-and-notifications/configuring-alert-notifications/setting-up-webhook-notifications/custom-webhook-messages for an example custom message to use for Microsoft Teams.
-
Don't check Agent status for Express Edition
Whenever I add a server to the monitoring that is Express Edition, I get alerted that the SQL Agent service is not running.
Well d'uh. It's Express Edition. The Agent service cannot run on it.Instead of always giving me this alert and then having me go in and disable it for yet another server, why not change the logic to not raise this alert at all when the edition is detected as Express?
3 votesThis was fixed in version 9.0.10 released on May 1st https://documentation.red-gate.com/sm9/release-notes-and-other-versions/sql-monitor-9-0-release-notes
Please update to the latest version and let us know if that does not solve the issue for you.
Thanks
SQL Monitor Team -
Commit to supporting Linux in some way
Linux is the future of sql server. If you've not deployed SQL 2019 AlwaysOn on Kubernetes I'd highly suggest you do. The install is lightning fast compared to clunky Windows installers of the past. I really feel like Redgate is taking a slow poison by not getting on this sooner. Honestly most of the metrics in sql monitor come from the internals of sql. All we really need from Linux is probably free disk space and cpu.
18 votes -
Add 2017 CU14 to Estate view
Currently SQL Monitor shows the latest SQL Server 2017 version to be CU13 yet the latest is CU14. This should show the latest version.
1 voteHi Mark,
Thanks for bringing this to our attention. This has been fixed and should now resume automatically updating once per day as long as the SQL Monitor website is still running.
If you need to manually update, you will find the instructions here: https://documentation.red-gate.com/sm9/estate/versioning-and-patching
Thanks again,
SQL Monitor Development Team -
SQL Agent jobs with a 'cancelled' status are incorrectly flagged as 'Job failing' in the Alert Inbox
With Always On related SQL Agent jobs, an initial job step is added to check whether the target database is Primary/Secondary on the cluster node. If 'Primary', then continue with subsequent job steps, if 'Secondary' then stop and do not attempt any further job steps. In circumstances where the job is stopped the last run outcome is shown as 'Canceled' - however, SQL Monitor shows these particular status jobs as 'Job failing' in the Alert Inbox. The job hasn't really failed and has been stopped in a controlled way. Can the status of these job be correctly identified please?
11 votesThanks for this suggestion, and for the additional comments which helped us decide quickly what solution to implement.
Version 9.0.13 released 23rd May includes a new Job cancelled alert (off by default) and stops the existing Job failing alert being raised for cancelled jobs.
We hope this meets requirements and will mark it as closed, but please do raise further suggestions for any improvements you would like to see.
Thanks,
SQL Monitor Development Team -
In the Estate view you are 2 CU's behind for SQL Server 2016.
Currently SQL Monitor shows the latest SQL Server 2016 version to be SP2 CU4 yet the latest is SP2 CU6. This should show the latest version.
1 vote
- Don't see your idea?