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.
- or
747 results found
-
Trigger Self Healing Script and Auto Close
It would be great if SQL Monitor could invoke a SQL script upon an alert threshold being crossed and then take action within itself (ie. clear itself, notify a team, etc) based on the value returned (0/1) or default to an action if there is an issue with the script execution.
This type of functionality would help administrators have a first line of defense before truly getting paged on an alert such as a drive filling (perhaps you have txt files you can purge or shrink logs (though I don't necessarily condone this, but you get the idea!)
27 votes -
Data retention - auto shrink if SQL
Recently engaged with redgate support about this and was advised to raise on here.
When changing data retention settings within Monitor and reducing the timeframe, it does free up space within the database but it isn't released.
Adding a routine within Monitor to run a shrinkfile against the database would be an ideal solution, but even adding a button/form within Monitor to set up a SQL agent job to do this in a standardised way would be fantastic as a quality of life, as if you're reducing the retention it's usually going to be because of disk space constraints.
2 votes -
1 vote
-
See Transaction Isolation Levels in Blocking Alerts
There are two methods I have been using to understand blocking situations on our servers:
The processes tab in the Blocking Process alert
The blocking processes section in the server overviewI can get a lot of information from both of these methods but I don't seem to be able to get the isolation levels of the blocking or blocked queries which would be helpful in understanding why the blocking situation has occurred.
Prior to using SQL monitor, we used the blocked process report to monitor blocking and these include the isolation levels. Unfortunately, I still have to…
1 vote -
Add a process that automatically checks to see if a stand-alone SQL Instance has become an Always-On Availability Group
There is a stand-alone SQL Instance that is being successfully monitored by SQL Monitor.
The SQL Instance importance has increased and the SQL Instance becomes an Always-On Availability Group. This change is not detected by SQL Monitor.
The work around is to remove the SQL Instance from being monitored and re-add, the SQL Instance for monitoring so that the change is detected.
Add a process that automatically checks to see if a stand-alone SQL Instance has become an Always-On Availability Group or has been removed from a Availability group to become a stand-alone instance once…
6 votes -
In SQL Monitor, I want to use a variable description in a custom alert.
Some custom metrics could be about things like a specific disk, job or DB-object. At this moment it's not possible to specify those in a generic Alert.
If besides the metric value a descriptive value was allowed, it would be possible to parse the descriptive value into the Alert.3 votes -
Allow for the conversion of time to to HH-MM-SEC in the Duration column on the Server Overview Page
Its difficult to always have to convert milliseconds, so it would be very handy if this conversion was an option to be included.
10 votes -
display unlicensed servers in different color
We started with RedGate Monitoring and added all our SQL Servers. As a result we consumed too much licenses. Although there's a warning on the top of the screen for this, the unlicensed servers are reporting 'healthy' which is a little tricky (especially for non-dba it'ers) because you don't know the state.
I like to see the unlicensed servers in a different color ( for example gray) to see a better reliable overview
6 votesUnlicensed servers are now shown as grey on the global dashboard.
-
Long Running Query Duration for Specific Queries
It would be really useful is this feature came into Live!
We have a number of queries that run on our SQL servers. We are aware these normally run for a long period of time (5-10 minutes) and do not want to exclude these from being alerted to us. Rather than changing the Long Running Query threshold for all the queries within the server we would like to be able to do it for these specific queries that take that little bit longer than others.
26 votes -
Alarm based on cumulative wait ms/s
The per server overview includes a graph of wait ms/s. I want to be able to set an alarm threshold based on Core Count and wait ms/s - If the server is waiting for more than 30% of total available cycles then raise an alarm
E.g. Server has 24 cores, and therefore 24,000 ms/s of available waits
Wait ms/s = 10,000 - 10,000 / 24,000 = 41.7% - ALARM
Wait ms/s = 2,500 - 2,500 / 24,000 = 10.4% - No alarm5 votes -
Change management for all changes made to your application and a report for the manager to review this change
Change management for all configuration change made in SQL Monitor and a report for the manager to review this change
4 votes -
3 votes
-
Report Poller Error - turn off the PFUR
There is an administrative event error in windows event log occurring every minute or less. This error is unrelated to report poller and is product feature usage reporting (PFUR) unsuccessfully reporting back to redgate. I have been assured this message is harmless, but I think anything that is happening every minute on the server is bound to have some detrimental effect.
Please add a feature to turn off this usage reporting.
3 votes -
See how alerts correlate in time
CONTEXT: When investigating an alert, it is useful to see what else has happened at the time. SQL Monitor gives detailed performance and query data with every alert details report, but doesn't show what other alerts have been raised at the time
PROBLEM: Sometimes alerts inform one another. E.g. a Long-running query can be caused by a blocked process, or a deadlock can cause a job failure. Alerts coinciding with the current one potentially help us to determine the root cause
EXAMPLE SOLUTIONS:
• List time-correlated alerts when viewing alert details
• See alerts over time on a graph
•…38 votesVersion 6.0 was released on August 30th, 2016 and contained a new Server Overview which shows alerts over time.
I am closing this as there have been no new comments since it was released. If you would like to see specific improvements to this feature, please raise a new suggestion.
Thanks,
SQL Monitor Development Team -
Allow Creation of time series charts based on alerts raised
There are times where you have an alerts such as low ple on a heavy use server, this will take several remedial measures to fix - having the ability to create time series charts showing amount of alerts raised over time for any particular alert on a particular server for a specified time frame would be helpful in assessing how affective any remedial actions are
7 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…
6 votes -
Feature for Integration of Redgate Monitor with Share point
Integration with SharePoint to display the dashboard without needing to login
1 vote -
compare query metrics across instances
I would like to be able to compare query metrics across SQL Server server instances.
We have a number of environments - Dev / QA / UAT / Production
the data generally increases in volume and gets more "real" the further up the chain we go which can mean something that performs well against the "small data" on the dev server can become an issue when it hits UAT which has real volumes of data
It would be useful to be able to compare a query across instances so if we release a feature which comprises of a number of…
5 votes -
add custom metric for tracking use of deprecated features
I think it should be possible, using Extended Events or some other method, to create a custom metric that allows SQL Monitor to track the use of deprecated features. This data is useful for upgrade planning or best practice reviews. I realize some of this can be found via server-side tracing, but I have heard that Extended Events may be more efficient.
1 voteWe tend to avoid sharing custom metrics that affect server state (such as creating a new XE). However, you can implement this yourself – the following article should point you in the right direction: https://www.mssqltips.com/sqlservertip/1857/identify-deprecated-sql-server-code-with-extended-events/
-
be able to add individual machines instead of an entire cluster
Right now when adding a node to Redgate Monitor and if it's part of a cluster, the entire cluster is added (even when switching off the auto-discovery of the clustername as this is only applied to the name itself).
Especially with large cluster estates, it's not possible to add a single node instead of the entire cluster.
This has impact on licenses, as the entire cluster needs to be licensed instead of each individual node that you actually want monitoring for.12 votes
- Don't see your idea?