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.
788 results found
-
Automatic failover when GEO replication is set up for PaaS servers
It would be great to have a feature to monitor automatic failover when GEO replication is set up between PaaS servers.
It is quite useful information to understand if failover occurs.
4 votes -
DatabaseName custom message parameter addition for Custom Webhook messages
I would like to share with the developers the alerts for the different databases we have in the same server instance. I noticed for custom webhook messages. It looks like the option was there (like monitoredEntity.azureSqlDatabaseName).
One of the SQL instances we have is a shared instance with multiple databases so the owner of the database can know exactly what database is failing
Right now I have the following custom message
{
"text": "{{alert-severity}}: An alert of type \"{{alert-name}}\" has been \"{{alert-status}}\" for {{alert-target-name}}.\r\nVisit {{alert-url}} for details."
}
Where I cannot specify which database is that alert for. I consider…
4 votes -
Display parameter list in the query plan form
It would be great to be able to see the parameter list from the query plan in the "Query Plan" form without having to download the plan and traversing the XML file.
It would save time troubleshooting problematic queries.
4 votes -
Report that shows top 50 long running queries across the estate
Submitting an enhancement request to expand the reporting capabilities for long running across the entire estate. The report tile only show a handful. It would be very useful to be able to run a report listing the top 25, 50, etc long running queries across the entire SQL estate. The data is available somewhere but instead of going into each instance a consolidated report would be greatly beneficial is order to identify queries for performance review. We are also going through an upgrade and are identifying queries to benchmark for before and after performance to ensure there is no degradation.
4 votes -
Add User Settings feature
Add a User Settings feature that will hold all user preferences, as different DBAs / users have different ways in using SQL Monitor. For example - (1) ability to display on the Overviews page only desired health levels (Critical, Warning, etc), or named group, or base monitor, or any combination, rather than load all servers from all groups from all base monitors. I really don't want to know that I have 265 healthy out of 275 servers - this will speed up loading of the Overviews page. (2) any other user preference.
4 votes -
Avg. lock wait time alert
Be able to have the Avg. lock wait time metric as a configurable alert.
this metric is already available in the analysis tab, but we can't define alert on it.
Avg. lock wait time
The average wait time (in milliseconds) for each lock that could not be satisfied immediately and had to wait for resources.Equivalent PerfMon counter: SQLServer:Locks - Average Wait Time (ms)
4 votes -
LDAPS Support for user authentication for Redgate SQL Monitor
LDAPS Support for user authentication for Redgate SQL Monitor . Now organization want to make the ldap communication to be more secure and moving to LDAPS communication . LDAP will be discontinued soon . When can this be implemented
4 votes -
Remove "Configure alert" link from alert emails
This is a big issue for me because I send Job Failure alert emails to the development team, but I don't want different people configuring alerts on Redgate Monitor. Only DBA's can make changes to the monitoring configuration.
I don't think the "View full alert details" is necessary either. If developers need to see more information, they can look at the Job History.
4 votes -
see username and hostname in "top 50 queries" and "top 10 waits"
In SQL Monitor, I want to see username and hostname in "top 50 queries" and "top 10 waits"
Please add username and hostname in "top 50 queries" and "top 10 waits." These two columns will be useful to trouble shoot SQLs that are causing troubles
Thanks,4 votes -
save monitoring data of a specific day
When having performance related issues on environments we'd like to be able to "save" the data of a specific day or days in order to do a proper root cause analysis, even over a longer period of time.
Due to aggregation of data we're now seeing issues arise that after a certain period we're no longer able to access detailed monitoring data of that day through SQL Monitor. Being able to access this data in SQL Monitor helps us correlate this data against other monitoring systems even after aggregation.
Our suggestion would be to add a save button for a…4 votes -
Alert Type for Polybase Service
Standard Alert Type for monitoring of the Polybase service status analogous to the other services (Browser, IIS, Agent, Full-Text, etc. )
4 votes -
Set a configurable delay to send the Resolved/Ended emails
Sometimes the emails sent by SQLmonitor to PagerDuty are delayed for some minutes
In this case it can happen that PagerDuty received the "Resolved/Ended" emails before the "Raised" emails because this one has been delayed for too long and because the alert was resolved after 1 or 2 minutes...
When it happening the alert is never closed and generate a useless phone call
So to fix this issue we would like to delay all the "Resolved/Ended" emails send by SQL monitor to be sure that PagerDuty received the "Raised" emails before "Resolved/Ended" emails4 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 -
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 -
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 -
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 -
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 -
Current Activity (sp_whoisactive) History
I would love to see snapshots of current activity (sp_whoisactive) taken on a regular cadence (e.g. every 5 minutes would be very useful for troubleshooting).
So in the current activity tab I can select a snapshot time from a dropdown of taken snapshot times. Backwards/Forward buttons advancing to the next/previous snapshot would very powerful.Having the top queries and waits etc. is super useful, but being able to see a snapshot of the active running queries around an incident would add a lot of value.
Appreciate that is potentially generating a significant volume of data so appropriate retention/default capture options/server…
4 votes -
Remove sys from Top Queries as a filter
On the dashboard “Top Queries” grid, a way to filter out any queries that were system wrote or 'sys' wrote. This way you can monitor only the queries that you have written.
4 votes -
implementing user permission settings at the instance level, rather than at the cluster level.
In my company, it is crucial to implement permission settings at the instance level, rather than at the cluster level, for accessing overviews and creating summarized reports. ~
This feature is extremely important because our clusters are shared by multiple tenants/instrances, and we need the ability to assign specific permissions to the respective owners of each instance.4 votes
- Don't see your idea?