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.
223 results found
-
Median from jobs - calculating Job duration unusual ONLY for sucess
I have noticed that SQL Monitor calculate median from all jobs ragardles if it is failed or sucess...
From my point of view it should analyse only jobs which finished success and calculate median from duration.
I need to know when job succeded what is duration median and if it is ok or not.Please change job duration median to calculate from jobs which ended with sucess.
3 votes -
Estate view (SQL Server version) Discrepancies
For the SQL 2016 versions of SQL Server, we are seeing the software is flagging as "not current". However, we do have the latest SP/GDR.
This issue lies with the Azure Connect Feature which only applies to connections to Azure based on an article we read. . (https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2016/build-versions)
We do not use Azure so we feel that this should not be a required patch.
3 votesAvailable from version 14.0.13 (July 19, 2024).
The Versions page under Estate will no longer recommend users to update instances of SQL Server 2016 to the latest Azure Connect Feature Pack GDR unless that instance is already using an earlier version of it.
-
Add field 'Description' to Powershell module manifest
Currently it is not possible to redistribute the powershell module to an internal nuget powershell repository, because the field 'Description' is missing in the psd1 file.
At the moment we need to add this field and sign the module again before publishing it to our internal nuget feed.3 votesThis is now available in Monitor.
-
Improve the resolution of the analysis graphs
The analysis graphs don't plot enough points to be able to clearly pick out peaks and troughs in the data -- it all gets averaged out.
2 votesAbsolutely. We’ve upped the resolution from 50 data points to 500 or so.
-
Ability set working hour for analysis graph
ability set working to compare last x day for only working hour
2 votesYou can already do that – just specify what your working hours are in the time selector boxes
-
Have ability to sort list of machines on the Analysis page and anywhere databases/machines are listed on SQL Instance overview
Have ability to sort list of machines on the Analysis page and anywhere databases/machines are listed
2 votesObject lists are now consistently sorted alphabetically
-
2 votes
Hi Ben,
Thanks for letting us know about this bug in our validation logic. It will be fixed in the upcoming version of SQL Monitor
-
2 votes
SQL Monitor V 3.3. has now released. This release contains improved subject lines and message bodies of alert emails to help you quickly understand problems before logging in to SQL Monitor.
Thanks,
SQL Monitor Development Team -
Summary alert page ordered by active alert type with drill down to detail
In the previous red gate alert program it had a summary by each alert giving a quantity for the selected monitor period and one could then drill down to the detail for that specific alert in chronological order starting with the most recent - found this most useful - also gave a simple measure of occurrences over time which one could use to track the effectiveness of efficiency projects
2 votesThanks for the suggestion – we believe this has been addressed with the Grouped Alerts released in Version 7.1.18.
We will close this suggestion, but please do raise another suggestion if you have other specific improvements you’d like to see.
Kind regards,
Adam
SQL Monitor Development Team -
A report on the front page (Overviews) of the Sql service status
A report on the front page (Overviews) of the Sql service status (Datbase Engine,Agnet,Reporting Service And etc )
Using DMV "SYS.DMSERVERSERVICES"
This Report includes Columns For Example : ServiceName,Startup-Type ,Status-Desc And Last Startup Time
Tnx From Redgate Company Team
2 votesUnhealthy service statuses raise alerts in SQL Monitor, which will be surfaced on the front page (future work on the front page will make this more parseable in SQL Monitor 5.2)
-
2 votes
Hi, thanks for this suggestion.
We have added a button to the query plan that allows the full in-truncated text to be copied to clipboard.
We hope this improvement solves the suggestion so will mark it as completed. Please do let us know if you have any further feedback.
Thanks,
SQL Monitor Development Team -
suppress emails during maintenance window
Allow the ability to suppress all alert emails during a maintenance window. Right now we have ~65 SQL servers and during windows when the OS team is patching and rebooting the servers we can receive 100's of emails as the servers go up and down. It would be great if we could set a schedule or at the very least a single use window when emails don't get sent.
2 votesThanks for this suggestion. SQL Monitor 10 now allows teams to suppress alerts, or just their notifications, over certain periods using alert suppression windows. Please see What’s New in SQL Monitor 10 for more details (https://www.red-gate.com/hub/product-learning/sql-monitor/whats-new-in-sql-monitor-10).
We hope this meets requirements and will mark it as completed. Please raise further suggestions for any improvements you would like to see.
Thanks,
SQL Monitor product team
-
Be able to identify Base Monitors by a user friendly name in a MSP Solution
For example in the "Manage Servers" screen, when using a MSP Solution, it's only possible to view the actual names entered on the Base Monitor Configuration page.
Without having to resort to a DNS work-around for this issue, it would be nice to add the option to use a "Display Friendly name" instead of the name of the Base Monitor Server.
That way, people who don't know which individual server belongs to which individual client or base monitor, can easily identify them based on their displayname.2 votesThis is now possible from version 11.0.4
-
Change "Blocking Processes" icon
To quicker navigate through the menus when collapsed, better distinct icons would be helpful.
2 votes -
Show job name not job ID value for job related alerts
When viewing SQL Agent job related alerts the identifier is the Id value stored in SQL Server, it would be more useful if this displayed the actual job name.
1 vote -
1 vote
-
Change colour of chart line
When viewing a single metric chart in 'Analysis', the line is a yellow-golden colour, which I find horrible (just my opinion) and hard to focus on - can this be configurable?
1 voteThis was completed in 3.0 – apologies for not updating sooner.
We changed the colour palette and improved it. We have still had to use yellow due to the number of dbs it’s possible to display, but it will be used last and is more of a mustard/orange yellow now. We’ve also deepened other colours so the Analysis page should be easier to view.
We hope this is fixes the problem – thanks for the suggestion – and we welcome any feedback.
-
Report average page life expectancy
The "page life expectancy" performance counter can be a good indicator of an impending performance problem. It's in the "Buffer Manager" performance object.
1 vote -
Invistigate v3.0 EAP Base Service CPU utilization
I first installed v2.3 and then switched to v3.0 EAP. It seems that the base service is maxing out CPU utilization which was not the case with 2.3.
1 voteMarking this as complete as it is a bug rather than enhancement/ feature request. Any bug related to EAP can be reported at eapmonitor@red-gate.com.
-
..retry operations that fail during install/ initial connection to server. Such as at my server where DBCC TRACEON (1204,-1) failed. In that
..retry operations that fail during install/ initial connection to server. Such as at my server where DBCC TRACEON (1204,-1) failed. In that case, retrying would be good, to ensure that it is eventually turned on.
1 vote
- Don't see your idea?