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.
788 results found
-
Display running SQL text instead of full batch
Hi Team,
Currently, Active Sessions displays the full batch text instead of the exact running SQL statement. It would be significantly more valuable to show the specific executing query text.
Having immediate visibility into the exact query would allow us to quickly identify blocking, long-running, or resource-intensive statements without relying on additional tools or manual investigation. This would reduce troubleshooting time, speed up incident response, and improve overall performance monitoring efficiency.
I believe this enhancement would provide clear operational benefits for teams managing busy production environments. Thank you for considering it.
6 votes -
Monitor Postgres Read-Only Replica Query Performance
PostgreSQL read replicas (standby servers) operate in read-only mode and do not allow writes. Because Redgate Monitor relies on writing to the redgatemonitor repository database on each instance, it cannot collect query performance data from read replicas.
In our environment, read replicas handle a significant portion of reporting and read workload capacity. Without visibility into query performance on these replicas, we lack critical insight for troubleshooting and capacity planning.
While tools like pgNow can monitor read replicas without requiring local writes, they do not provide the historical performance data and trend analysis available in Redgate Monitor.
We are requesting support…
6 votes -
Allow Creation of time series charts based on alerts raised
There are times where you have an alerts such as low ple on a heavy use server, this will take several remedial measures to fix - having the ability to create time series charts showing amount of alerts raised over time for any particular alert on a particular server for a specified time frame would be helpful in assessing how affective any remedial actions are
6 votes -
Ability to set up multiple webhooks
We are generating a work flow where alerts of a specific type are sent to a seperate monitoring tools and the rest to a google chat - both use webhooks, both to different locations - at the moment we are using a work around with script tasks....but ideally being able to set different webhook locations and message for different alert types would be beneficial
6 votes -
custom group order
I'd like to be able to pick an order of my groups... dev, prod, staging in alpha I'd prefer to see prod, staging, dev.
5 votes -
Allow configuration of Fragmentation Alerts down to Table for EXCLUSIONS
The Fragmentation Alert for a database only permits on/off and low/medium/high with page count configurations.
This is far, far too high a level to be useful.
The Alert needs, at the very least, INCLUSION and EXCLUSION capabilities by table within database. An overall fragmentation low/medium/high and pages would be OK to START WITH, but It would be great to be able to go to each index and state the fragmentation limits and even whether to monitor it.
In my case, I use Idera's excellent Defrag Manager, so when I see this alert, I check that Defrag Manager is doing its…
5 votes -
Make software FIPS 140-2 compliant
Currently SQL Monitor is not FIPS 140-2 compliant
5 votes -
Ability to change the width of list of metrics at analysis page
The small width of list of metrics makes difficult to read list of metric if it has metrics with names over 20 chars. See attached screenshot.
5 votes -
Group / Sort custom metrics
We have a lot of custom metrics and the current interface is not robust, being able to group / sort metrics in folders or in a tree would be very useful. Also the selection box in the analysis tab is not large enough to navigate a useful number of custom metrics
5 votes -
I only have one SQL Server, take me to the instance Overview instead of global dashboard
I only have one SQL Server instance, instead of seeing one small bit of info and having to click that in the new global dashboard, take me directly into the instance so I can get relevant info on first login/site visit. Think about your design when we just have one server.
5 votes -
Keep from Locking Account When Registering Server with wrong password
The process of registering a server should try only once with a credential failure, looks like it keeps on trying and if you have typed in a wrong AD password it will lock your account.
5 votes -
Apply filters to more SQL Server alerts
In configuring Long Running Query, I'm able to specify a filter on the process name (e.g. wanted to exclude my "Barracuda" backup processes - and did so successfully). I'd like to do the same for other Alerts such as Deadlocks and Blocking Processes.
5 votes -
Restrict the read only role to only the "Overview" page.
I've explored using Read Only views for SQL Monitor and they work great, while really parring down the amount of information that the user can see. However, is there are way to lock it down even further so that they can only see the homescreen with the colored status on the specified SQL Instances? Essentially only allowing them to see status without drilling down into the instance itself and viewing waits, disk, CPU etc.
This could be used by management, etc.
5 votes -
Exclude tempdb/ReportServerTempDB from Alerts at a GLOBAL level, WITH EASE
It makes no sense for there to be Alert configuration settings for tempdb for Consistency Checks, Backups, and any other irrelevance.
If the ONLY reason for the existence of SSRS databases is because of Microsoft's idiotic requirement for SSRS to actually be configured in 2014 before permitting an in-place upgrade to 2016, there is no ACTUAL reason why one would care two hoots about the state of either SSRS DB on ANY instance affected by this "demand". OK, I have just 21 instances to drill down to SHUT UP ABOUT SSRS DATABASES!
Please provide a better way to manage SYSTEM…
5 votes -
Option to include @Channel or @User in Slack Channel Notification
Provide an option for individual alerts to include @Channel or @User to the slack channel notification.
5 votes -
Display on TV screen
Hi, We run Yodeck boxes to display content on TV's
This has a scripting function to pass some logon details
It would be good if I could have a read only view of the server dashboard or help identify the submit button to script it
Ive tried - Only the password is enteredtype("""#password""","""MYPASSWORD""")
click("""#remember-password""")
click("""#submit""")5 votes -
Monitor entity framework queries
as the query generated by entity framework are different, we need a way to monito the queries and group them in a similar bucket
5 votes -
Select Database
Select Database
When Selected Instance And Add For Monitoring . I can not Selected/Unselected Database For Monitoring.
If possible, add this feature.5 votes -
Show current RPO
Show current backup RPO and allow us to click the graph to see specific databases under each RPO grouping (>15 minutes, >30 minutes, etc).
5 votes -
Overview - Drill-through ability on Splits/sec to the Queries causing it
So we get to the "Analysis" page when clicking on a peak in the Page Splits/sec graph. But that tells me the same thing, in larger form, but not the root cause...
It's the root cause of 20K/sec I'm after... So, please give us the CHOICE of drill-through, to the responsible queries grid, or some other place. It's only useful if the ACTUAL queries causing the splits are listed, not just a repetition of the top-10.
Thanks.
5 votes
- Don't see your idea?