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
723 results found
-
Webhook Filter on Alert Severtiy
Situation: After setting up a webhook of SQL Monitor to Service Now we are getting tickets of all priorities
Background: We would only like tickets to be created that are actionable
Assessment: We can enable this on the javascript side of the service now webhook to remove low priority webhook calls however it would be prefered to do it in RedGate
Recommendation: Is it possible to have the same feature that email has "Call webhooks only if alert severity is High or Medium only"
9 votes -
Longest queries which are running on each server.
Right now we are getting only 4 queries. Also, if we check Database, these are only the system databases, Actual databases are not considered here.
Our requirement is to get the Longest queries which are running on each server. After getting these details performance optimisation team is going to check those queries and try to optimise them. Can we get these details?1 vote -
Customize email alert recurrence to receive it more often
Have an option to change how often I want the email alerts to come. Let's say I want to track the alert for every, and I mean every, SQL job failure. Everytime a job fails, even when I intentionally fail it, I want to receive a mail.
3 votes -
Set a custom alert for a individual tracked query
We can track query's from the analysis page - good for when you want to see how a query changes over time. What would be even better would be to be able to set an alert on a tracked query on any metric but for example, the execution time so we can get an early alert if it is taking a long time to execute and it's business critical
1 vote -
contained
Add support for Contained Availability Groups (CAG) in SQL Server 2022
This is actually a feature that broke with the new version. There is no ability to monitor SQL Agent Jobs.10 votes -
Produce a long running queries report ordered by average execution time
I have been tasked with identifying queries with the longest average execution time so that they can be targeted for optimization. In the server overview this can be done in the top queries section, however this obviously only shows queries for that instance.
In the reporting tab I can create a report for long running queries, but it is based around total execution time. It would be useful if this could be ordered by average execution time.
A query that runs 100,000 times and takes 10ms will have a higher overall execution time than one that runs 50 times and takes 10s, however this is the one that we think would benefit most from optimization.
I have been tasked with identifying queries with the longest average execution time so that they can be targeted for optimization. In the server overview this can be done in the top queries section, however this obviously only shows queries for that instance.
In the reporting tab I can create a report for long running queries, but it is based around total execution time. It would be useful if this could be ordered by average execution time.
A query that runs 100,000 times and takes 10ms will have a higher overall execution time than one that runs 50 times and…
1 vote -
Add Top Waits info for PostgreSQL
Re: PostgreSQL Monitoring
Please add the ability to show wait stats by wait type as you have for SQL Server.
3 votes -
Show login and client hostname/IP address for Top Queries on PostgreSQL
Re: PostgreSQL Monitoring
Please add information about the connection that the queries (in the Top Queries section) were executed on, specifically the client machine hostname/ IP address and the login name.
4 votes -
Job failing Alert option for number of consecutive failures in a row
I have some SQL Agent jobs that run every 2 minutes and legitimately fail occasionally to circumstances outside our control.
I need to be alerted if the job is constantly failing, e.g. failed 5 times in a row, but I do not care about one off failures.Having a customisable option for individual jobs to alert only after X consecutive failures would be fantastic.
3 votes -
Show query history for custom date range in "Top Queries" view
In the top queries window, the history can only be searched via three date ranges:
Zoom Range,
Window Range,
All historyIt would be good to be able to search a custom date range to make the graph easier to see for a time period of interest. Window range is only three days max and all time can be too broad.
5 votes -
Provide Managed identity as an Authentication Method to the Redgate Azure SQL DB
Support for using the managed identity of the Webserver/Applicationserver VM to authenticate over the AAD on the Azure SQL Redgate Database.
-> Maybe also Support for Azure App Service which has built-in this functionality?
3 votes -
Monitor DB2 Databases
I would like to be able to monitor DB2 databases in the same fashion as SQL Server databases.
6 votes -
Monitor Oracle Databases
I would like to be able to monitor Oracle databases in the same fashion as SQL Server databases.
6 votes -
Clear RedGate Alerts automatically
Once the alert is taken care of, RedGate should send an email saying that the alert is cleared. Also, there is no need of a clear button in the web interface, it should be done automatically.
2 votes -
Estate Licensing - Align with Microsoft HA/DR Licensing policy
Estate licensing appears to tally all licenses for servers in an WFC/HA config. 3 node cluster 4 cores, 12 licenses (when it should be 8). Please provide the process to identify an HA or DR node, which will allow the Redgate Estate portal to align with Microsoft SQL Licensing: https://download.microsoft.com/download/e/2/9/e29a9331-965d-4faa-bd2e-7c1db7cd8348/SQL_Server_2019_Licensing_guide.pdf.
3 votes -
Mask sensitive data from deadlock and top queries
We want to let developers use SQL Monitor, but for that sensitive data has to be masked. Two places that come in mind where we can things like literals in WHERE clause etc are deadlock and top queries. This would ideally be combined with a security group which which the masking should apply.
6 votes -
be able to set top level notification settings through powershell module
I want to be able to use Redgatesqm.ps1 to configure smtp server, default email list and other top level notification options.
1 vote -
Only Query Serverless Azure SQL Databases if they are Online and not Paused
As mentioned in the below post, SQL Monitor will keep serverless Azure SQL databases from pausing and saving us the money they are supposed to. I would like the Azure SQL monitoring piece to be rewritten to use the Azure API to determine both if the Azure SQL DB is serverless or not and if it is AND paused, don't run any queries that would wake it. Yet if it is NOT paused, get info about it and update SQL Monitor.
4 votes -
Job Duration Unusual Alert should be 'AG aware' to avoid false positives
We are using an AG for one of our instances.
As you would expect we have the same SQLAgent jobs created on both instances in this AG, but we only want the job to execute on the primary.
In SQLAgent the jobs on both nodes of the AG have a step at the beginning which checks to see if this is the primary instance.
If it is the primary instance it will proceed to step 2 and execute the rest of the job.
If it is not the primary instance the job will terminate.
This all works fine - however the Job Duration Unusual alert does not take AG failovers into consideration.
For example, we have a job that normally takes around 13 minutes to complete on the primary instance.
All the executions of the job on the secondary instance take less than 1 minute, as they are simply checking the AG then terminating.
After a failover, when this becomes the primary instance, they start taking 13 minutes.
But this alert uses the 1 minute executions in its calculation of the baseline, so is continually alerting us that the job is taking considerably longer than the baseline.Is it possible for the Job Duration Unusual alerts to be aware of the AG and calculate its baseline based on the last 10 executions of the job on the primary instance, so that it uses an accurate baseline when calculating deviation from the norm?
An alternative to the above could be to make the Job Duration Unusual alert more configurable, as mentioned in a different suggestion.
We are using an AG for one of our instances.
As you would expect we have the same SQLAgent jobs created on both instances in this AG, but we only want the job to execute on the primary.
In SQLAgent the jobs on both nodes of the AG have a step at the beginning which checks to see if this is the primary instance.
If it is the primary instance it will proceed to step 2 and execute the rest of the job.
If it is not the primary instance the job will terminate.
This all works fine - however…2 votes -
Ability to filter "TOP Queries" by login
Often we want to filter queries not only per existing options (database, parent or query) but it's useful to be able to search for a specific login.
Could you allow searching by login using "l:" or "login:"?
11 votes
- Don't see your idea?