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.
- or
769 results found
-
slack
Auto resolve slack after alert status is ended or cleared
6 votes -
Error Log Section - Under the instance screen add a search function similar to Databases section where we can search for keywords like fail
Error Log Section - Under the instance screen add a search function similar to Databases section where we can search for keywords like failed logins. This will speed up the process to look for something specific rather than moving through pages looking for that one error.
1 vote -
Report - Longest running queries: Include Stored Procedure name
Please include the name of the stored procedure (where applicable) in the report of "Longest running queries".
Currently I need to use SQL Search to find the procedure that includes the query.You can do a LEFT OUTER JOIN sys.objects using objectid to find the name (objectname) of the originating stored procedure.
30 votes -
bring Failed SQL Agent Jobs to the front
Show Failed SQL Agent Jobs at the first. Currently its behind (graphic)
For us its important to see the Failed Jobs.
6 votes -
Slack notification in more detailed
Slack notifies the alert, would be great to view complete details in slack specific to notified. This helps giving access to development for a slack channel to look into Long Running Query corresponding to database. without giving full access
8 votes -
Set Maintenance Window by Group
We do maintenance by class of server (DEV, QA PRD) and update an entire group during one maintenance window. It would be nice to be able to select a group like "Production" and set one maintenance window instead of setting it for each server. And since we do maintenance on the second Sunday for one group and the third Sunday for another we can't set a window and forget it. We have to set it before the weekend there will be work done and then clear it on the following Monday. More scheduling flexibility would be a wonderful addition.
4 votes -
I am making reports in the Red Gate SQL Monitor. I am organizing them by databases in AGs. This is difficult because when selecting what dat
I am making reports in the Red Gate SQL Monitor. I am organizing them by databases in AGs. This is difficult because when selecting what database to monitor it is either ALL on server or an individual one. I have to put a new line for each database I want. Could you please also include "ALL in AG xxx". This way I do not have to add a line for each database in the AG I am monitoring, and if I add or take away a database from that AG then it will automatically be done on the report.
1 vote -
Estate Page - Disk Usage - Show Actual with Allocated
There's plenty of real-estate to include a column for database file rows that shows the true "USED" space, not the Allocated space.
Right now, SQM is predicting data drive exhaustion at 16 days hence:
Fake "Used": 5,634.5 GB Capacity: 5,959.4 GB Fake "% Used": 95% Time until full: in 16 daysSadly, Untrue, from a "Used" perspective - only true from an Allocated perspective!
When I drill into that drive, THIS is the truth:
Used: 4,752.6 GB Capacity: 5,611.7 GBPlease promote this "USED" as a higher-level total, and use it as a projection - i.e., retain a history of USED by DB drive and project from THAT, not from allocated. (misnamed column on the main page needs fixing)
This saves "serious problem here" knee-jerk reactions from the main page, forcing the SQM User to drill-down only to find, "no problem here".
Thanks.
There's plenty of real-estate to include a column for database file rows that shows the true "USED" space, not the Allocated space.
Right now, SQM is predicting data drive exhaustion at 16 days hence:
Fake "Used": 5,634.5 GB Capacity: 5,959.4 GB Fake "% Used": 95% Time until full: in 16 daysSadly, Untrue, from a "Used" perspective - only true from an Allocated perspective!
When I drill into that drive, THIS is the truth:
Used: 4,752.6 GB Capacity: 5,611.7 GBPlease promote this "USED" as a higher-level total, and use it as a projection - i.e., retain a history of…
4 votes -
full table scans
Highlight full table scans on big tables, so these can be investigated
It could be these tables have grown, so initially they were ok, but now they aren't
3 votes -
Alarm based on cumulative wait ms/s
The per server overview includes a graph of wait ms/s. I want to be able to set an alarm threshold based on Core Count and wait ms/s - If the server is waiting for more than 30% of total available cycles then raise an alarm
E.g. Server has 24 cores, and therefore 24,000 ms/s of available waits
Wait ms/s = 10,000 - 10,000 / 24,000 = 41.7% - ALARM
Wait ms/s = 2,500 - 2,500 / 24,000 = 10.4% - No alarm5 votes -
Add free-format text when emailing an Alert
When I email a DEADLOCK to a team member familiar with, or responsible for, the functional area, for them to get a "blind" DEADLOCK email, bearing no introductory narrative, saying nothing about frequency, or suggesting that mitigation code be added where known to not be present, means I have to email to myself, compose the extras, and forward.
The ability to add a header-block to the email, with a polite sign-off, is more likely to engage, than for the recipient to have to start asking unnecessary questions.
3 votes -
Utilize SQL (or SQL-like) statements in filters.
Utilize SQL (or SQL-like) statements in the filters, specifically on the Overview tab to filter on server name. For example: '%sql%' AND '%prod%'
Currently you can only do 1 fuzzy logic search. Also, you cannot search just by one character.24 votes -
ignore events triggered from SIEM vulnerability scanners..
when we run a vulnerability scan on our SQL servers we get a lot of redgate alerts, i know you can setup to ignore certain alerts and have a maintenance window but ignoring the alerts isn't an option (what if its actually a hack) and the maintenance window is dangerous for obvious reasons.
3 votes -
Change Processor Utilization per instance
Currently i have 4 instances which are part of an availability group and run maintenance as various times. although different maintenance windows would be nice to have the flexibility of changing Processor Utilization per instance rather than per cluster.
6 votes -
Custom disk alerts in a cluster is lost when instance is moved to a new host
We often use customized disk alerts for larger disks i.e. instead of using the default alerts we might configure a High alert at 200 GB and a medium at 250 GB.
These custom alerts is not set on the instance level so when we move the instance to a new host the custom alerts will not follow the instance and the alert has to be set up again.
As our largest cluster is 9 node cluster with 23 instances and 3 disk each this cause us to configure these alerts at a maximum of 621 instead of 69 times. That is a huge difference.
Would it be possible to tell SQL Monitor that a specific alert is an “Instance configure alert” instead of a Host alert and that it should overrides the Host alerts? Alternatively, some other solution.
Thanks! /Ted
We often use customized disk alerts for larger disks i.e. instead of using the default alerts we might configure a High alert at 200 GB and a medium at 250 GB.
These custom alerts is not set on the instance level so when we move the instance to a new host the custom alerts will not follow the instance and the alert has to be set up again.
As our largest cluster is 9 node cluster with 23 instances and 3 disk each this cause us to configure these alerts at a maximum of 621 instead of 69 times. That…
21 votes -
Exclude individual databases entirely from scope
There are some databases (including the RedGateMonitor database) that i do not want to see reported with alerts. I want the ability to omit certain databases entirely from the scope of monitoring and leave all other databases on that machine in the scope of monitoring/alerts.
5 votes -
Report Poller Error - turn off the PFUR
There is an administrative event error in windows event log occurring every minute or less. This error is unrelated to report poller and is product feature usage reporting (PFUR) unsuccessfully reporting back to redgate. I have been assured this message is harmless, but I think anything that is happening every minute on the server is bound to have some detrimental effect.
Please add a feature to turn off this usage reporting.
3 votes -
Wider parameters for reports
Incorporate ability to run reports for a group of monitored servers for a longer duration. For example: Report of unreachable status on 12 different servers for the past year.
1 vote -
Support 3rd party HA tools such as DxEnterprise
3rd party HA tools such as DxEnterprise allow for failover of a virtual host (VHOST) from one Server (virtual or physical) to another in the event something happens to the VHOST. In the failover process, it will pull all of the associated disks along with the VHOST to the new machine it is going to be hosted on. If RedGate SQL Monitor is configured to monitor the physical server, things work well until you need to fail over. Then you get alerts of disk changing from 20% free to 0 bytes free and the failed-over SQL instance(s) are no longer being monitored.
The alternate configuration is to set up redgate to monitor the VHOST. This works a lot better for monitoring the SQL instance after failover, but results in disk drives and SQL instances appearing in duplicate when more than 1 VHOST exists on a server. For example, if we have our reporting instance on VHOST reports and our SSIS on VHOST ssis both hosted on physical machine PM1 and we notice that the report server is using up a lot of memory and causing delayed with SSIS package execution, we may choose to fail ssis over during the busy reporting times to PM2. SQL Monitor will freak out if we do that though telling us that ALL of the VHOSTS on PM1 suddenly lost the associated disk for that and we will get alerts that are not valid.
While we could turn off the low disk alerts, having them off means we won't get ANY low disk alerts which is a problem as well.
The other problem is if ssis and reports are both on PM1 and ssis has a 20 GB S drive, because both vhosts have the same drive letter and GUID, the SQL Monitor reports show that the S drive has 40 GB which is not accurate.
I am not sure of a good solution to supporting a tool like DxEnterprise would be, but my initial thoughts are to have the configuration for the disk monitoring and instance monitoring be more configurable and selective. For example, I may only want to monitor disk S on ssis but not monitor disk S on reports. And some disks I don't want to monitor at all as they are managed by the IT department (C drive, page file drive, etc).The short version of this suggestion is to have more user control over what SQL Monitor monitors.
3rd party HA tools such as DxEnterprise allow for failover of a virtual host (VHOST) from one Server (virtual or physical) to another in the event something happens to the VHOST. In the failover process, it will pull all of the associated disks along with the VHOST to the new machine it is going to be hosted on. If RedGate SQL Monitor is configured to monitor the physical server, things work well until you need to fail over. Then you get alerts of disk changing from 20% free to 0 bytes free and the failed-over SQL instance(s) are no longer…
3 votes -
Alternate color background on dashboard server groups
Could you add some alternating color background to different server groups on the overview dashboard so the swimlanes are much easier to distinguish
1 vote
- Don't see your idea?