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.
686 results found
-
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 -
monitor specific services status and specific event logs entrys
this would really be useful to monitor specific windows services status and related event log entry's (even filtering them would be nice)
specially since the is no other way to monitor microsoft dynamics nav (navision)
sql part is helpful but when the problem are on the nav service tiers or schedulers theres no way to check than manually.6 votes -
Allow users access to view specific reports
Currently I create a few reports for different business areas and e-mail them daily. It would be really useful if they could follow the link on the page and view their reports only without having access to the site in general. They could then use the report filters.
Another idea would be to be able to create a reports page with a static link where I could put several different reports, users would have access to this page only and be able to view any reports created in real time.6 votes -
View queries against specific database in real time
View all running queries against a specific database with the details of the query and its duration.
This will help in monitoring a specific query in any particular time
17 votes -
Make alert configuration levels more discoverable
CONTEXT: In SQL Monitor, you can configure alert behaviour down to the object level (such as the Database or the Job level). This is useful e.g. when we have specific databases with different backup policies to our global configuration, since we can specifiy "special rules" for individual databases.
PROBLEM: It is counterintuitive how to do so, and many people don't spot the left-hand drilldown navigation - this makes you think that you can only configure on the global and the server level! Also, when we have created an override, it's easy to forget so causes surprise when we change the…
172 votescurrently under investigation
-
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 -
Install SQL Monitor without needing to provision a (large) SQL Server database
CONTEXT: One challenge with installing SQL Monitor is that we need to provide a connection to a SQL Server database.
PROBLEM: This can be costly or complicated. It would be better if SQL Monitor had an alternative backend.
EXAMPLE SOLUTIONS:
• Offer a hosted data store
• Automatically deploy a free backend alternative such as mongoDB or PostgreSQL
• Reduce data collection so that SQL Express can be used for small deployments
• Provide greater granularity over data retention policiesWhat do you think about these solutions? Got another idea? Let us know in the comments!
153 votes
Adam
responded
We’ve made some improvements in this area but will leave it open so you can continue to give us your suggestions
-
Monitor Azure SQL DWH
It'd be great to be able to monitor performance of queries on Azure SQL DWH, as there are a number of DMV's available to track usage. Also, the ability to see on the Dashboard what DWU level the Azure DWH instance is running on would raise value and awareness of the cost of it, at that point.
13 votes -
Desktop notifications
Desktop notifications would have (at least) 2 advantages:
1) It would give much quicker access to the critical alert information than a regular alert email, since you could layout/format the notification with perfect flexibility (as opposed to default email client notifications which devote most of the real estate to the "from" address, and subject and body in plain text)
2) With a couple buttons, the notification could give immediate access to actions such as "clear" or "mark as read"
13 votes -
Monitor SSAS databases
I would like to be able to monitor SSAS cubes and data structures in the same fashion as SQL databases.
53 votes -
Resize the columns
Be able to dynamically resize, refit columns so details could be seen.
4 votes -
See disk percentage free/used to Machine overview page
It would be useful to see disk percentage free/used on the machine overview page next to the used / allocated column. This would give us a quick idea of how full the machine's disk is percentage-wise without having to do the math elsewhere.
17 votes -
Reduce false positives due to log shipping / Mirroring
On secondary server for log shipping/mirroring false positives can be generated for overdue backups/databases unavailable. If these technologies are used for DR purposes then having the checks ignored is unsafe. It is trivial to filter these out with the below code and I'm sure there is something similar in place for Availability Group databases already.
SELECT *
FROM sys.databases
WHERE name NOT IN (SELECT secondarydatabase FROM msdb.dbo.logshippingsecondarydatabases UNION SELECT dbname(databaseid) FROM msdb.sys.databasemirroring WHERE mirroringrole_desc = 'MIRROR')18 votes -
Use extended events instead of trace when trace initialized due to alert
I have seen a related idea https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/5717202-use-extended-events-for-deadlock-tracing-instead
However, I'm expanding this. If the SQL version is high enough the trace of current activity should be using extended events instead of a trace, this would reduce the total impact to the server performance while also expanding the available information.
98 votes
Daniel Rothig
responded
Thanks for the suggestion – we’ll monitor how popular it gets
-
Drop markers on the graphs and add annotations
While working on performance tweaks it is customary to consult the analysis reports on a regular basis to see if our changes moved the needle. More often than not the tweaks are released one small batch at a time and it'd be nice to drop markers and custom annotations directly on the charts. I'd like to use that feature to add short phrases describing what was changed that led to the improvement, or degradation for that matter, of performance.
This would be by server (cluster/node) and by metric with the same retention period as the base data for that chart.
…
61 votes -
Keep from Locking Account When Registering Server with wrong password
The process of registering a server should try only once with a credential failure, looks like it keeps on trying and if you have typed in a wrong AD password it will lock your account.
5 votes -
Filter "Blocking Process" alert by User or Application or Database
We frequently get high-severity "Blocking process" alerts via email for a SSRS database that I'd like to ignore. We sometimes get so many alerts that the new SQL Monitor sends, "You've received more than 30 of these alerts in the past 24 hours so we're going to stop sending them for a while." Unfortunately the alerts caused by the SSRS database mean our Inbox is full of noise and we miss our important application database alerts.
Please add the ability to filter which User/Application/Database cause these alerts to be raised, similar to some other alerts that support Regular Expression filters.
14 votes -
Simpler Upgrade \ Patch Process
The upgrade process is a bit long winded. It would be great if the system could be upgraded or patch with a single click. Ideally within SQL Monitor but if not, downloading the file and just selecting upgrade would be great.
70 votesDaniel Rothig
responded
Thanks Phil – we are considering reworking the upgrade process. If this suggestions gains more traction, we’ll prioritise it higher
-
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 alerts32 votes -
Show a log of query activity
CONTEXT: When investigating a performance issue, I want to know what has been running
PROBLEM: SQL Monitor has rich query information on the overview screens, the performance diagnostics panels, and the query alerts, and the query trace in alert detail reports, but it's difficult to tie that information together
EXAMPLE SOLUTIONS:
- Implement a query log
- Show query information on the analysis graph45 votes
- Don't see your idea?