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.
793 results found
-
Configurable Alert Thresholds for notification alerts
I would like to suggest a new alerting feature for Redgate Monitor: the ability to configure notification thresholds based on the number of consecutive occurrences of an event.
For example, for SQL Server Agent Job failures, it would be useful to define a threshold so that an alert is triggered only after a job has failed a specified number of consecutive times (e.g., 3 or 5 failures), rather than generating a notification for every individual failure.
This enhancement could help reduce alert fatigue and notification noise, especially in environments where occasional transient failures may occur and do not require immediate…
30 votes -
Security team needs a report how SQL instance compliance has been met
In the Security -> Server Compliance:
Need the capacity to email or subscribe the "SQL Server Compliance Report (csv) which displays drilldown the SQL Server Compliance values of the Server property in the selected Server Compliance template for each instance (tabs).There is export button, but it doesn't have the option to drill down the status for each instance. Also, it is not subscribable.
4 votes -
Changes to Alerts when VCenter monitoring is interrupted
Today's RG Monitor includes vCenter integration for monitoring resources. This is a great feature that we really enjoy using. But, when there is a problem with vCenter or it is otherwise unavailable for maintenance, we get a generic internal monitoring error for every single instance we have monitored. This creates a lot of unnecessary and unuseful noise that needs to be investigated. We'd much prefer to see a custom alert specific to the VCenter object. The alert could be disabled for individual servers if we didn't want their status affected by vcenter status. Alternatively, the alert could attach to a…
3 votes -
Add Key Lookups to the SQL Server metrics
Though Page Splits and Full scans are useful metrics for index's, key lookups can be handy in finding areas where covering indexes are required and have been helpful in seeing where there is a regressed query from a bad plan - this would be a handy metric to have within the SQL Server metrics part of the main dashboard next to the other 2 mentioned.
21 votes -
Allow ServiceNow notifications to be filtered by alert severity
We are using the native ServiceNow integration in Redgate Monitor to automatically create and resolve ServiceNow alerts.
Currently, ServiceNow notifications are generated regardless of the alert severity. We would like to be able to configure a severity threshold for ServiceNow notifications, in the same way as for other notification channels.
For example, we would like to configure the ServiceNow integration to create alerts only for High severity events, with options such as:
All alert levels
High and Medium
High onlyThis functionality is particularly important for ServiceNow integrations, where every notification may result in a ticket or operational event. Sending…
6 votes -
log_reuse_wait_desc value is captured and stored within the database page (click on a DB in the databases section to get there)
logreusewait_desc value is captured and stored within the database page (click on a DB in the databases section to get there)
would help investigating why a log grows
6 votes -
Update should keep ;MultiSubnetFailover=true in the connection string
Currently, SQL Monitor DB is on the SQL Server cluster, in the availability group.
When I'm doing the application update, the update process reads old connection string (<add name="DataConnectionString" connectionString="Data Source=ops-sqlmonitor-ag.ad.npspot.com,6803;Initial Catalog=OPS-SQLMonitor;User ID=RedGateSQLMonitor;Password=***************; Max Pool Size=500;Connect Timeout=5;Encrypt=False;Trust Server Certificate=True;Packet Size=4096;MultiSubnetFailover=true"/>) from the config file, but when it writes it back, it has removed the ";MultiSubnetFailover=true" -part.
This means the connection to the DB may not work because DNS returns multiple IP addresses, and the first IP address isn't always the primary node.
4 votes -
Suppress Notifications until turned back on
There are times where we are configuring and testing an instance or cluster and want to monitor it, but would like to prevent notifications being fired while keeping alerts - having the ability to suppress the notifications until we turn it back on would be handy and take less administration overhead than configuring the alerts for each instance/cluster
14 votes -
option to Enable AI on selected SQL instances and Logging AI activity
it would be very useful to control which SQL instances have AI enabled. Perhaps an opt out or opt in under Monitored Servers
Even if data is said not to be sent from prem to LLM, enabling logging of the AI traffic per SQL instance, would go a long way ifor management buy in
6 votes -
Monitor sessions and stats on an Oracle Active Data Guard (open read only)
Currently, if you set up an Oracle Active Data Guard database in Red Gate, it detects that it is a standby database and doesn't gather any usage, session, activity, or other data from it. However since the database is open for read, there is session data, performance data, and other metrics created that are unique to this database. Basically, the request is to monitor an Active Data Guard database as a standalone database (with the caveat that it is read only).
If Red Gate could gather those stats without requiring sysdba privileges or connection to the primary that would be…
6 votes -
be able to see in Redgate Monitor who changed the status of an alert
We have a certain way of working with the tool and all of a sudden, a whole bunch of alerts that were marked 'read' (and what we think are worth looking at) are switched to 'read' ... and thus are no longer looked into ... as they are off the map. I can't figure out who made the status change right now. It would be a big plus if we could have status auditing in Redgate Monitor.
7 votes -
on the Query executions page add the SPID
on the query execution page for individual queries can you add the query SPID - on occasions such as blocking/stale session etc you need to find the query/last ran query by SPID rather than start/end time
16 votes -
Add Cname as a connection string instead of instance name
RGM usually connects with the instance name it automatically pulls down via the WMIC commands it runs on the nodes -There may be times were you have set the systems up that all connection certificates used the CNAME set up rather than the instance name for connection
Adding the ability to replace the instance name with a CNAME for connection will allow RGM to connect to the server securely18 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
8 votes -
Azure Service Principal authentication (Client ID / Client Secret)
It would be highly beneficial for us if Redgate Base Monitor supported authentication via Azure Service Principals using Client ID and Client Secret across all Azure products, including Azure SQL Database and Azure SQL Managed Instance.
We are restricted to using Service Principals only and cannot rely on user-based authentication. Support for SPN authentication would allow us to fully automate the onboarding of new Azure SQL Databases and Managed Instances via Terraform, using our own modules, and register them in Redgate without any manual interaction. This would significantly improve scalability, consistency, and security in our Azure monitoring setup.
16 votes -
Make the alerting system AG Aware
Similar in nature to the Job Duration Unusual Alert should be AG aware - there are many alerts we do not want to see on an AG secondary unless it is set to readable - things like server waits due to queries running on master etc generate alerts when running against a base line but we dont need to get the alert/notification if the AG is set to secondary
9 votes -
update MS teams channel alerting to send alerts to various channels and not just a single channel
Much like when using SMTP alerts, can you add the ability to specify an alternative channel for alerts sent from a specific server or group of servers.
for example, if I have 2 groups of severs,
- producion alerts to channel 1
- non-productions server alerts to channel 2the core issue is we have multiple "products" monitored (production and non-production) and
we don't want the noise from the first product to be visible to the second, or third products.Currenly we use email groups for this but with changes in O365 we are under pressure to stop using SMTP.
2 votes -
Add ability to monitor MongoDB instances on atlas
Though Atlas does supply its own monitoring tool - having the ability to have a single pane of glass for all services by having the ability to monitor MongoDB which are hosted on atlas within redgate would be beneficial
13 votes -
Blocking Process Alert to be based on Blocking Time
This idea has been posted before but marked as closed, so posting again. For blocking process alert, it would be good to have the option to setup the alert in a way where we can report on the duration when the first and last blocking happened and if it exceeds a certain threshold.
Let's say, we have set the threshold for 90 seconds and if there are three processes that have wait time of 30 seconds each, that totals to 90 seconds, we receive an alert. However, we don’t want to receive an alert for the 30 second blocked processes.…
24 votes -
Monitor SQL Fabric from Redgate Monitor
As our company leans into Microsoft Fabric, we'd love to continue utilizing Redgate's tools, but unfortunately, they're mostly incompatible. Our highest priority is the ability to monitor Fabric SQL from within Redgate Monitor, closely followed by Redgate Toolbelt functionality within SSMS. We love Redgate and we're moving into the future with Fabric. Please help us remain a dedicated customer and not have to look for additional tools. We love Redgate!
20 votes
- Don't see your idea?