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.
711 results found
-
have more flexibility with user permissions.
I'd like to be able to customize permissions. For instance, I would like an AD group to have the ability to set and remove alert suppressions (operational) but not have admin access to the monitor (administrative).
2 votes -
Monitoring of Windows Server Failover Cluster
We would like to have the option to monitor Windows Server Failover Clusters as an integrated part of SQL Monitor. Considering that over 50% of our infrastructure is implemented as Always On High Availability Groups, operating on WSFC, we would like to have monitoring and alerts if something on WSFC level goes wrong such as a node disconnecting, a File Share Witness going down, errors reported in the WSFC console etc... At the moment, if something happens at WSFC, such as loosing quorum due to a file share witness going down, we are not being alerted and will not know…
7 votes -
Trigger a device check-in via powershell
We use powershell scripts to shut down and start SQL services before and after maintenance. The scripts create a suppression window before and after as well. However, if the suppression window is removed too soon after the services are up, alerts are still fired because SQL Monitor thinks the server is still down. We workaround this by adding a delay in the scripts, but it's annoying to sit and wait for it. I'd like to be able to force SQL Monitor to check in with the server before removing the alert suppression window.
3 votes -
Control Alerts For Managed Instances Separately From On Prem.
Some guidance for Azure SQL Managed Instances is different from on prem SQL Instances. For instance, there is information out there not to just do routine index maintenance and instead do statistics and only rebuild indexes when there is an obvious problem. Having a way to keep our current alerts for on prem and turn this off for Azure would be helpful.
1 vote
Neil Turner
responded
Hi Tom,
Thanks for your suggestion. Can you provide a bit more context for your suggestion? What goal are you trying to accomplish?
Would the current ability to control alert settings by group not be sufficient for this?
Thanks,
Neil
(SQL Monitor product designer) -
Provide a tile for an Availability group on the main page
Should be able to see status of an availability group from the front page
8 votes -
Monitor repliction
Monitor replication (same as replication monitor)
5 votes -
Monitor SSRS
Monitor Reporting services
3 votes -
Database name "like" filter for "Database Unavailable" alert
In our environment we have several systems (3rd party ETL/reporting packages) that create and drop databases as part of their normal operation.
Would be good if the "Database Unavailable" alert allowed configuring to ignore drops of database names either matching a "LIKE" filter or perhaps more advanced a regex filter.
12 votes -
In the backup check would like it if we could select the times of the backup to then show that group
in the Estate > backup page you are able to see issues such as RPO 1 week. it would be good to be able to click on this to then show the backups listed (fade the not appropriate backups).
6 votes -
With the AG Groups it would be good to have soft alerting on configurations
With the AG it is possible to have different configuration on the server replicas. We mostly get caught out with Logins. but have had issues with XMLBlob size, linked servers and Server Master Keys.
It would be good for monitor to alert (or be able to alert) if a Login does not exist on both (all) replicas. we have times when a quick addition through SSMS does not put the same login on all side. when fail over occurs we then have broken processing. It would be good for sids to be checked as well as this is another issue…
6 votes -
We would like to send slack messages to different channels depending on the server.
We have multiple teams who are ultimately interested in what is wrong with their platform, The posting to a single slack channel is good, however giving an option to send only messages from certain servers to specific channels would improve our customer engagement. currently the main channel is ignored by the all teams except the dba's as the chaff from other servers can cause disinterest, or interest when no reason for a team to investigate.
9 votes -
PaaS dbs on an instance appear seperately
Hi Redgate Support,
While adding PaaS SQL servers, each database appears individually. Will this change in near future where they appear together with other database on the instance like they do on-prem and on IaaS.1 vote -
Word Wrap Alert Comments
Super minor detail, but it would be a more pleasant experience if I didn't have to use a scroll bar to read comments on Alerts. If it were word wrapped in some manner it would make the user experience better for me.
5 votes -
Select custom date range in Estate - SQL Agent Jobs
Would like to be able to view SQL Agent Jobs between dates. Currently you can pick from Day - Week - Month but it would be really good to have "Custom" also which allows you to select start and end date.
90 votes -
Ability to not monitor/show certain queries in the TOP 50 list.
The top 50 query view in SQL monitor is showing the query that is running on the service broker queue with explicit waitfor statement. In our server these waitfor is 5 min and we have 100 threads that runs for 5 minute and wait for the messages in the queue.
The query monitor shows these query as the top slow performing queries, but in reality these are not slow queries, they are just waiting for messages in the queue. We need a way to not show up the queries in top 50 list, so the queries that are actually slow…7 votes -
I'd like it to be more obvious that an active alert is no longer a current and unresolved issue
Whenever an issue is flagged, for example in the night, it changed the server to red. Once you click on that, the state is "active" (more un acknowledged I would say if not current). For me it is not clear if that issue is still ongoing or that it had been an issue and is now resolved.
Can it be made clear what the end time is if the alert is no longer active? (right now only start time is listed)2 votes -
In SQL Monitor, I want to use a variable description in a custom alert.
Some custom metrics could be about things like a specific disk, job or DB-object. At this moment it's not possible to specify those in a generic Alert.
If besides the metric value a descriptive value was allowed, it would be possible to parse the descriptive value into the Alert.3 votes -
Automatic validation of regex for Long-running query configuration
When applying regex filters for long-running queries, a malformed expressions causes the page to just drop the error and not take the save action.
My suggestion is to just implement a basic regex validation and prompt/indication on error.2 votes -
Disable specific alert for some time
Make it possible to ignore a specific alert for a specific server for x amount of time. Sometimes there is something going on for say half a day and you do not want to miss out on other errors but just that specific one.
2 votes -
FCI alerts should refer to the DB instance and not to the active node
For various alerts that are actually assigned to nodes of a Windows FailOver cluster (no AlwaysOn), the alert display shows the active nodes as the source. For example, "Disk average read time" Node1 -> E: instead of the cluster role SQL instance -> E:.
I can more quickly deduce from the name of the DB instance which DBs or which applications could be affected. The names of the nodes are numbered and meaningless.
1 vote
- Don't see your idea?