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
716 results found
-
Alerting on Autogrowth Events
Alerting on Autogrowth Events, some environments set the file size of their databases and would like to be alerted if autogrowth occurs since that indicates abnormal behavior
3 votes -
Export/Import Report configurations
I'm using RedGate SQL server with different clients. Since the environments are not connected I have to manually create Report configurations for each client which takes quite some time. Also, any change to the Report configurations has to be then deployed by cilcking. Some export to XML or something similar and import wia PowerShell API would be nice.
23 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 -
Define limit of the specific job alert.
problem : a job is running in every 2 mins and failed due to any reason .it will fire multiple alert ,I would like to restrict the limit of the specific failure
solution :as we work in the shifts , I want it should not come more then 3 time which is in 8-9 hours duration .when I am setting the limit then it will impact to all server not the specific one . whereas I would like to check this monitor based on the time and then fire the alert
3 votes -
Include drive letter in subject and body of disk space alert email
It would be helpful to know which drive (by letter) the alert information detail is about in the email. The drive letter should be included in the subject line such as Disk space | ServerName | E:\ as well as in the body of the email. This information helps identify the problem drive without having to go to SQL Monitor for that information.
15 votesThis enhancement will be in the next version of SQL Monitor
-
3 votes
-
Add Top Waits info for PostgreSQL
Re: PostgreSQL Monitoring
Please add the ability to show wait stats by wait type as you have for SQL Server.
3 votes -
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 -
Add an analysis metric for Total bytes sent/received over the network interfaces
There is an analysis metric that currently exists for Network Utilization, which I believe is calculated based on the total bytes sent/received over the network interfaces divided by the bandwidth of the network interface. It would be great to add the raw delta bytes/megabytes sent/received/total as a metric on the analysis and overview pages of Sql monitor.
14 votes -
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 -
SQL Agent jobs with a 'cancelled' status are incorrectly flagged as 'Job failing' in the Alert Inbox
With Always On related SQL Agent jobs, an initial job step is added to check whether the target database is Primary/Secondary on the cluster node. If 'Primary', then continue with subsequent job steps, if 'Secondary' then stop and do not attempt any further job steps. In circumstances where the job is stopped the last run outcome is shown as 'Canceled' - however, SQL Monitor shows these particular status jobs as 'Job failing' in the Alert Inbox. The job hasn't really failed and has been stopped in a controlled way. Can the status of these job be correctly identified please?
11 votesThanks for this suggestion, and for the additional comments which helped us decide quickly what solution to implement.
Version 9.0.13 released 23rd May includes a new Job cancelled alert (off by default) and stops the existing Job failing alert being raised for cancelled jobs.
We hope this meets requirements and will mark it as closed, but please do raise further suggestions for any improvements you would like to see.
Thanks,
SQL Monitor Development Team -
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 -
Feature for Integration of Redgate Monitor with Share point
Integration with SharePoint to display the dashboard without needing to login
1 vote -
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 -
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.
-
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 -
1 vote
-
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 -
Latch Wait Time Explanation
In SQL Monitor 4.0, the explanation refers to sys.dmdboperational_stats which does not actually exist.
Should this be sys.dmdbindexoperationalstats?
4 votes(not actually declined, but we are tracking this separately as a bug)
-
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
- Don't see your idea?