Suggestions
Welcome to the Redgate SQL Monitor feature suggestions list. Tell us how we can improve SQL Monitor by voting on these suggestions or by submitting your own ideas.
This is the easiest way to make an impact on SQL 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 — often the SQL Monitor team will initially stay quiet about new suggestions to see what you have to say!
If you have any questions visit the SQL Monitor forum.
655 results found
-
Group instances, not servers
For example: when I have a database cluster running multiple instances I would want have the possibility to put one instance in a development group and another instance from that same cluster in a different group. In this way managing alert settings etc on a group level becomes much more convenient.
33 votes -
allow more configuration options for the 'Job duration unusual' alert
The 'Job duration unusual' alert is based off of the last ten runs of a job. I think allowing a configurable number of runs to be a baseline or better yet, the last x runs at the same time of day would be ideal.
33 votes -
be able to report on deadlocks
Add the possibility to report on deadlocks. The information is stored in the database as an alert but it's currently not possible to report on alerts.
I'd like to see the occurrence of deadlocks over time, per database,...
32 votes -
Create alert on items in Analysis Graph
The ability to create an alert metric around data which is currently being collected for the Analysis graphs. E.g. Being able to alert when the BufferPagerLifeExpectancy drops below a certain amount.
32 votes
Daniel Rothig
responded
-
Have audible alerts on SQL Monitor
It would be very helpful to have a configuration setting to make alerts audible (something like a beep or alarm ring). In the office we have a screen that displays the SQL Monitor where the alerts are only noticed when people look at the screen, which is not very often.
An audible alert of 'red' alerts would prompt us to action them straight the way.
32 votes -
The ability to exclude nodes in a cluster I don't want to monitor.
When a cluster spans regions I want to be able to only monitor my "active" region and note my "passive/DR" region.
If my primary region fails I would like to switch over my licenses to the other region in SQL Monitor so that I retain my license count.
32 votes -
Save DMV Snapshots for Analyzing and monitoring changes
Idea is to save snapshots of DMV's so that the changes can be analyzed. For example sys.dmexecprocedure_stats shows only total, last and average elapsed time. It will be great to know how the average changed over a period of time.
Common use case: sysproperties
31 votes -
Add development machines without a license.
You should be able to add development machines at no additional cost if you already have a production license. If you do not have a license for the development instance then the features can be scaled back to only allow you to view alerts.
31 votes -
Utilize in SQL Monitor Analysis or Reports pages any SQL Server counter available in PERFMON.
For instance BRENT OZAR has an excellent method to diagnose memory pressure. The counter in use is SQLServer: Memory Manager – Memory Grants Pending which is not available.
If Memory Grants Pending is averaging over 0, queries can’t even start because they can’t get enough memory. You may have queries that have incorrect memory grants, or you may just desperately need more RAM.
30 votes -
Get the proc name from a deadlock alert
The Alert gives objectId and databaseid but your average 'accidental DBA' doesn't know the command
select OBJECTNAME ( objectid [, database_id ] )
Perhaps somehow suggesting the command as context sensitive help?30 votes -
Select different purge data ranges depening of what group a server belongs to.
We have different data retention requirements depending on what server is being monitored, but currently only 1 purge setting is available which covers all servers. An example of what I'd like to see would be to select to purge data older than 14 days for production/critical servers and a much shorter retention of data for test/development servers. This would be controlled by what group a server was a member of.
30 votes -
Filter Top 10 queries/waits by database
I would like to see the top 10 queries by database sometimes instead of the entire instance.
30 votes -
Make comments apply to alert types, rather than individual incidents
CONTEXT: We use comments to document the root cause of alerts we encounter
PROBLEM: When alerts repeat, recovering the comments is a pain - they only apply to individual occurences, so don't get surfaced when they issues re-occur.
EXAMPLE SOLUIONS:
- Show historical comments in alerts
- When creating alerts, allow us to choose whether this applies to the whole alert typeADDITIONAL CONSIDERATIONS:
Comments should also show when configuring alerts30 votes -
Add COMPARE BASELINE option to the Reports in SQL Monitor
In SQL Monitor 6.0.17.6667 the new Reporting feature is terrific, however I would like to see the addition to add the COMPARE BASELINE option to the Reports like Analysis option currently has. This would allow us to see if measurements like CPU, user connections etc are in line with a baseline of, say last week or way off.
30 votes -
Alert on long I/O operation
Hosting Company raised an alert that there is absolutely no trace of as an issue according to SQL Monitor:
ALERT NAME: Rackspace - SQL I/O Error
TIME: 6/22/2011 7:02:21 PM
REASON:
Event Description: SQL Server has encountered 174 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [M:\xcp_trans.mdf] in database [xcp_trans] (5). The OS file handle is 0x0000000000000BBC. The offset of the latest long I/O is: 0x000023b6d20000
SEVERITY: CRITICALPlease augment SQL Monitor to do the equivalent alerting.
30 votesDaniel Rothig
responded
Custom metrics on sys.dm_io_virtual_file_stats are the best way to get this today
-
Different email addresses for different thresholds
Although you can specify different thresholds for High, Medium and Low alerts, they all end up at the same email address or slack channel. It would be useful to be able to change this so highs went to one address, mediums to another etc.
29 votes -
Show all of the cluster disk's collected statistics regardless of active node
Currently, a cluster disk's collected statistics are only visible for the duration of being "active/owned" by a cluster node. If I ran on Node A for the last month and fail-over to the B node today then I lose all visibility to the prior month's stats since they were collected while on the node A.
29 votes -
See on the overview page incase of a AlwaysOn or a windows cluster which node is the active\primary
We have several windows clusters and AlwaysOn clusters. It would be very helpful to see on the overview page which node is active.
It can be easily done by adding a color to the AG icon on the tile.
I know that it can be seen on the cluster overview but I really think it belongs on the Overview page.
29 votes -
Report - Longest running queries: Include Stored Procedure name
Please include the name of the stored procedure (where applicable) in the report of "Longest running queries".
Currently I need to use SQL Search to find the procedure that includes the query.You can do a LEFT OUTER JOIN sys.objects using objectid to find the name (objectname) of the originating stored procedure.
29 votes -
network adapter name on overview page
Currently network adapters' interface description is shown on the overview page of a monitored server. i am not interested of that information really, I would see the net adapter name as Get-NetAdapter cmdlet returns. So, Name should be there instead of the description.
28 votes
- Don't see your idea?