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.
779 results found
-
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.
10 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…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 -
Add date to legend when filtering across multiple days
When we filter on the top graph across multiple days, on the legend below won't show the days, just the time.
The image is the current case.
What I would like is to have the days.
Instead of "from 08:18 to 08:19"
expected "from 18 Jun 08:18 to 19 Jun 08:19" or equivalent4 votes -
AG sync progress
Implement Availability Group data synchronization progress.
We use Automatic seeding and stats can be observed under "sys.dmhadrautomaticseeding" and "sys.dmhadrphysicalseeding_stats".
Maybe that info not 100% accurate when Traceflag 9567 is ON, but anyway somehow helpful1 vote -
Schedule hourly reports to email out and base on groups
I would like to be able to send hourly email report for example Failed sql agent jobs base on a group not just one server, covering certain period of time like 9-5 each day of the week Monday- Friday.
5 votes -
Expiring Certificates
Would really helpful to have an alert for expiring certificates on a cert be it backup encryption ones or tde certs that are going to be expiring and we specifies how much notice we want given before the expiry
14 votes -
Long Running Open SSMS Transaction
Would be really helpful to have an alert that can alert on long running open SSMS transaction and the alert can return the user running it and query being run and on what server we often see it when users forget to commit or role back there transaction.
4 votes -
Use a private route for AWS RDS instances to remove the need for a public endpoint to monitor the instance
The current configuration only allows for the specific format my-db-identifier.random-chars.aws-region.rds.amazonaws.com / my-db-identifier.random-chars.rds.aws-region.amazonaws.com.cn. We would like the ability to use any dns name to allow intra-cloud or hybrid cloud scenarios for the ability to use a private/internal route to the RDS instance so that we do not have to use the public route for monitoring.
3 votes -
Add ability to collapse the "Query details"/"Wait type"/"User memory" list under a specific query.
Often we want to screenshot the execution pattern, the graph below all these areas and because all of those occupy a big chunk of space on the screen, this becomes harder.
We end by "zoom-out", crops, or even picking multiple screenshots and doing collages.
Thanks
2 votes -
Add the ability to use "special" characters (@, #, etc) when using searching in "Top Queries"
Hi, I'm trying to search some query patterns on the "Top Queries" grid for example "INSERT INTO @" or "INSERT INTO #" (to get all inserts on table variables or temp tables) however, in both situations, the @ and the # is being ignored.
Please include those (and other chars) to refine our searches.
Not sure if "RegEx" would be another option that would be even broader.
Thanks
3 votes -
Monitor Cluster Shared Volumes
Under the “Analysis” section, there are cluster metrics which include four different options relating to Cluster Shared Volume usage.
• Used Bytes
• Used %
• Free Bytes
• Free %If we click on the above, we can review our CSV’s to see whether we are approaching the drives maximum capacity.
What isn’t included is the performance of the disk. For instance, under the Machine metrics section, the following is available:-• Disk avg read time
• Disk avg write time
• Disk read bytes/sec
• Disk write bytes/sec
• Disk transfers/sec
• Avg disk queue length.However, these…
10 votes -
“Longest Running Queries” in Redgate SQL Monitor Reports
I need to show more “Longest Running Queries” in Redgate SQL Monitor Reports. The layout of the report is also a bit awkward, it seems if everything does not fit into the report.
See attachment.10 votes -
Being able to filter "TOP Queries" by any of the columns
On the "TOP Queries" grid we can order it by any of the columns (besides "Database").
I would like to be able to filter the rows by the amounts.
Example:
Filter queries where "Execution count > 100" same for other columns.
Then apply the "order by".This way we can filter together with the "Enter search term" box.
6 votes -
Ability to add notes to tracked queries
When working in an environment with multiple people is typical that each person is tracking different queries to analyse ongoing changes/improvements.
Being able to note something as "Tracked by Cláudio. Following FIX #1234" would be great.
It will give us a clue on who is working on what and reach out to that person. Or just keep small notes during the analyses.
15 votesA great suggestion. We are exploring this as part of a wider review into improving query tuning features.
-
Grant more granular report level access
I can grant report level access to a user by adding them to the Reports User role and I can restrict the servers which they see reports for.
However, this role gives the user more permissions than I would like to give - they can still view any other page - alerts, server overview etc
Can we change this so they can see the reports only?
2 votes -
Modifying of several alerts for specific entity could be more user friendly
1) after change tree in left panel with all servers collapse and again should expand nodes down to place where I left
2) color of changed records could be more visible, maybe some light background could be added4 votes -
Number of rows returned by query
I'd like the ability to view the number of row returned by a query. Tools like Dynatace, XRebel, New Relic are able to display this and it's extremely useful in identifying queries that are selecting too many rows and in need for application logic / code rework.
1 vote -
Have a free-text notes field for each server\instance
A notes field can be used for any useful information such as business contacts, service hours or documentation links, etc.
16 votes -
Long-Running Query Alert - Occurrences tab to refer only to instances of that query
In the long running query alert, the occurrence tab shows a history of occurrences of the long running query alert. These alerts are the history of any long-running query rather than just the query in the alert
It would be helpful to be able to see a long running query alert and see just the alerts for that query to be able to quickly understand whether this query is a regular problem, or something new.
I appreciate it is possible by highlighting the time period in the server overview page, finding the query and then viewing the query history but…
4 votes
- Don't see your idea?