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
724 results found
-
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.
2 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 -
Alert for Available Space on Backup Disk
There is a configurable alert for when disk space assigned to a logical disk reaches a threshold but not an alert for backup disk assigned to a disk other than the logical disk.
3 votes -
Configure Alert-Ended messages at alert type level
in the global settings I can configure, that I want to receive deescalation mails when an alert ended (e.g. CPU went back to normal, Server available again ...).
For many alerts this makes sense, but for other alerts not so much or not for everybody (e.g. deadlock alerts, the custom failed-logins alert, job-failed alerts...).
So it would be nice, if I could configure this (as most other options) at least at alert type level or better down on group / server / database etc.
6 votes -
Monitor Backups LSNs in Always On Availability Groups
With Always on Availability Groups, Error is... Log backup for database "XXX" on a secondary replica failed because the last backup LSN from the primary database is greater than the current local redo LSN. And SQL Monitor cannot check for this. I would like to see if SQL monitor can catch it before the Azure Backup Vault fails to backup every 15 minutes.
3 votes -
Be able to monitor Basic Availability Groups. Currently Basic Availability Groups are not supported
Be able to monitor Basic Availability Groups. Currently Basic Availability Groups are not supported
30 votes -
It would be nice to be able to exclude names of databases to be backed up instead of un clicking them one at a time .
It would be nice to be able to exclude names of databases to be backed up instead of un clicking them one at a time .
This should be similar to the long running queries where you have the option to exclude.1 vote -
Be able to customize alerts by job
I would like to be able to customize alerts by job. For instance, I have many jobs that run multiple times per hour. If it fails once or twice, I don't want to be alerted about it. However, if it fails 3+ times in a row, I want to be alerted.
3 votes -
Include more details regarding a disk space usage/free report
What I'm looking for is that for today, the D: drive is this filesize, e.g. 500gb. Once the report runs again the following week, it is 505 gb and so on. Then it would summarize that there is a differential of 5 gb which is the growth.
1 vote -
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?