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.
695 results found
-
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 -
Group / Sort custom metrics
We have a lot of custom metrics and the current interface is not robust, being able to group / sort metrics in folders or in a tree would be very useful. Also the selection box in the analysis tab is not large enough to navigate a useful number of custom metrics
5 votes -
SQL Monitor self update (or one click update)
Instead of downloading and running a wizard, I would like to see a way for SQL Monitor to self update, or to have a 'one click' update button built in the interface.
29 votes -
Quick view of whether Agent is up on all monitored servers
If I go to the Configuration > Monitored servers tab, I can quickly see if all SQL Servers are up and running. It would be nice to also be able to quickly see if all SQL Server Agent services are up and running.
3 votes -
SQL Monitore: I would like to see the response time I/O of database files.
SQL Monitore: I would like to see the response time I/O of database files. Currently it is showing only on instance level but how can I see response time of a particular
database.11 votes -
Alert based upon trend data
We want to be able to alert when a value changes dramatically over a period of time. so if a system returns 110,105,112,40,38,52
to eye ball that on a graph I can see there is a problem, however that may be at the peak time of the day and 38 might be a reasonable value for in the middle of the night, so having a threshold of a low value is not appropriate, the comparison mode of query for this situation would report a change of
-5,+7,-72,-2,+14in here there is one large drop but then it is running stable,…
3 votes -
Filter disk space alerts for Quourum disks
Add a new criteria to the Disk monitoring, that allows me NOT to monitor disks that have less than X GB/MB of Total disk space.
13 votes -
Allow trace to be set at the individual alert level and severity
SQL Trace can highly impact the performance of the server. I can't benefit from trace right now as it's set on any alert to launch a trace.
Other monitoring tools, for instance Sql Sentry, allow the individual alert to be configured with settings for trace.
For example: A long running job might benefit from a trace, while a "dbcc checkdb " hasn't been run in a long time should not trigger a trace. This increases storage and server load for no benefit.
Please look into allowing traces to be configured based on the alert AND the severity level defined on…
6 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 -
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 -
Control Alerts Using Metadata
CONTEXT: We have a maintenance and backup solution which uses SQL Server as a backend to determine what databases to perform the tasks against, and at what time.
PROBLEM: Some databases do not have maintenance tasks running against them, but still have alerts which appear in SQL Monitor for them (e.g. Index Fragmentation). I don't want to manually exclude these from SQL Monitor, as the number of databases fluctuates, particularly on our testing and development environments.
EXAMPLE SOLUTIONS:
- Provide a means of easily enabling/disabling/changing alerts dynamically using a stored procedure.1 vote
Daniel Rothig
responded
For your usecase I recommend modifying the maintenance window metadata instead:
UPDATE s SET MW_IsEnabled = 1, —or 0 to enable alerts again MW_Start=0, —midnight MW_Duration=864000000000, —24 hours MW_Monday = 1, MW_Tuesday =1, MW_Wednesday=1, MW_Thursday=1, MW_Friday=1, MW_Saturday=1, MW_Sunday=1 FROM [settings].[SqlServers] s INNER JOIN [settings].[Clusters] c ON c.Id = s.ParentId WHERE c.Name = ‘hostname’ AND s.Name = ’’ —Set to SQL Server name or leave empty for unnamed instancesA restart of the base monitor service will be required after the change
-
Baseline machine metrics across cluster failovers
CONTEXT: Using the Analysis graph for historical performance analysis of machine metrics on a cluster that failed over at least once
PROBLEM: Machine metrics are collected per node. Baselines of only one node can be shown at a time, and so no baseline view of performance on the "active" component can be synthesised.
EXAMPLE SOLUTIONS:
• Enable multiple simultaneous baselines
• Implement synthetic (bimodal) baselines across cluster nodes
• Provide synthetic metrics for entites on the "active" component of a clusterWhat do you think about these solutions? Got another idea? Let us know in the comments!
18 votes -
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 -
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.
71 votesDaniel Rothig
responded
Thanks Phil – we are considering reworking the upgrade process. If this suggestions gains more traction, we’ll prioritise it higher
-
Analysis parsing of dates and multiple baselines using a text input search
Allow the analysis and other date filters to provide the option to paste and try parsing the date based on matching common patterns (maybe even allowing user to define options in config file).
For example, the standard SQL datetime2(0) of yyyy-MM-dd HH:mm:ss pasted would convert to the date it parses.
Maybe even consider taking a page from the freaking great design Simple Bank has started applying which is a text based filter applying friendly syntax. I have found this incredibly useful.
They let you type in the search filter
"last 3 months"
"last week"
"date:1/1/2015-1/15/2015"
"date:1/1/15-1/15/15"and it immediate updates…
3 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 votesDaniel Rothig
responded
Thanks for the suggestion – we’ll monitor how popular it gets
-
comment markdown
CONTEXT: I use comments on alerts raised by SQL Monitor to document root cause of the triggered condition and resolution action.
PROBLEM: Comments only support plain-text. When creating/reviewing comments, it's often useful to add links for more detailed descriptions of the cause of the alerts, and links to ticketing systems for resolution steps. Simplified bulleting/numbering and bold/italicized text would also be helpful for breaking up monotonous text.
EXAMPLE SOLUTIONS: Add Markdown (http://daringfireball.net/projects/markdown/) support to addition/review of comments. A couple implementations for examples of usage:
- StackOverflow (http://stackoverflow.com/editing-help)
- GitHub (https://help.github.com/articles/github-flavored-markdown/)
4 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
-
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…
173 votescurrently under investigation
-
Select and store a static baseline for future reference
CONTEXT: When comparing server performance over longer periods of time or across deployments, the baseline functionality in SQL Monitor's analysis section is useful.
PROBLEM: SQL Monitor creates a dynamic baseline based on previous data. While this baseline is a realistic idea of what's "normal" it requires us to keep a lot of data in SQL Monitor
EXAMPLE SOLUTIONS:
• Aggregate data in SQL Monitor so that it can be retained for longer without using much space
• Allow us to "freeze" a baseline so that the data doesn't get deleted.What do you think about these solutions? Got another idea?…
41 votes
- Don't see your idea?