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.
682 results found
-
shortened neat sharing links for graphs etc
shortened neat sharing links for graphs
3 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 -
Filter out Long Running Query alerts based on wait type
We have a 3rd party product that has a SQL Database. It has something in it that loads data RBAR (Row-By-Agonising-Row). The query gets all the data in about 3 seconds and then sits waiting on ASYNCNETWORKIO for ages (close to 40 minutes).
We don't want to exclude the application from all long running query alerts, and the query is different everytime which would make it hard to filter based on regex (and not filter other queries we care about).
We'd like a way that we can not raise a long running query alert if it's waiting on…
11 votes -
Monitor Hyper-V hosts
https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/2936441-identify-if-virtualization-hosts-are-congested is closed, so I'm opening a new suggestion - please add the ability to monitor Hyper-V hosts, similarly as we can currently monitor VMware hosts.
19 votes -
Group sql server instances at the instance level, not at the server/cluster level
I would like to control the group that an individual sql server instance is in, rather then having to group things at the server/cluster level. The group views and control over alerting is great, but in the event that the same cluster/server hosts a dev and production instance, or multiple instances that are managed by different members of a DBA team,the usefulness really suffers.
8 votes -
export the overview page
The reporting is very limited and provides less detail that the overview and estate pages. We need to be able to export the overview and estate pages easily. Also need to be able to report on the Top queries and top waits.
8 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 -
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 -
Use error messages from SSIS catalogue
When a job fails, which is run from SSIS Catalogue, then the error message is basically "look in SSIS Catalogue", which is not very useful. I suggest using the error message from the [SSISDB].[catalog].[event_messages] view instead for these cases.
In our home made monitoring system we're checking the subsystem in sysjobsteps, then use the command from there to identify the dtsx package name and looking up the latest message from [SSISDB].[catalog].[event_messages] for that package for the error message.
21 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 -
Force re-check of index fragmentation alert
The index fragmentation alert is checked only once per week, because of the load is causes on the system. I am fine with that.
However, I would like to have the option to force an immediate re-check for a specific database - for instance by adding a "re-check" button to the alert window.SCENARIO: The index fragmentation check runs on Saturday and triggers an alert on one database. On Monday I check the alert but I know that the weekly index defragmentation job runs on Sunday, so it is likely that the problem is already fixed. But I like to…
11 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 -
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 -
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 -
Allow for the conversion of time to to HH-MM-SEC in the Duration column on the Server Overview Page
Its difficult to always have to convert milliseconds, so it would be very handy if this conversion was an option to be included.
10 votes -
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…
3 votes -
Add development machines without a license.
You should be able to add development machines at no additional cost if you already have a production license. If you do not have a license for the development instance then the features can be scaled back to only allow you to view alerts.
34 votes -
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.
5 votes
- Don't see your idea?