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
-
Access custom metrics via the Enterprise API
We need to visualize metrics on central dashboards - the Enterprise API is PERFECT for that - except it currently does not support access to custom metrics.
Custom metrics are one of the most powerful things Redgate Monitor has - we really need the ability to access ALL of our information outside of the Redgate tool itself.
2 votes -
Overview screen show as a list
Show the overview screen as a list of servers. If you have a large number of servers to be monitored, there is no way to see all of them at once (other than zooming out of the screen). It defeats the purpose of monitoring if you can't see everything.
4 votes -
increase or decrease the fill factor
Dear team.
I see some explanation on the sql Monitor live Demo tool which seems incorrect:
Check also: The fill factor percentage of the tables in your indexes. If enough space for index expansion is available on data pages, the potential for page splits is reduced. The default fill factor value setting is 0 (100%), which means that pages are filled to capacity. If you increase the fill factor, additional free space is left in the indexes after they are rebuilt or reorganized, helping to prevent excessive page splitting
increase should be decrease: the higher the fill factor the less…
4 votes -
Long-running query alert - add an option to exclude queries based on the USER running it
This alert already has the options to exclude queries (via RegEx) based on the process name or SQL commands/objects used. I miss a similar option for excluding queries based on the user running the query.
An example: let's say you have a job that runs SSIS job steps using a proxy->credential->dedicated domain user. The SSIS packages run loads of SQL queries, some taking a long time - but that might be expected and OK (let's say the job is a nightly ETL process for a DW). Without excluding queries based on that user (simple but effective!) you could get a…
64 votesThis was added in version 10.1.2 – you’ll see the option in the Long Running Query alert configuration screen if you update to that version or later. Thanks for the suggestion (and also to everyone who added comments)!
-
Use error messages from SSIS catalogue
When a job fails, which is run from SSIS Catalogue, then the error message is basically "look in SSIS Catalogue", which is not very useful. I suggest using the error message from the [SSISDB].[catalog].[event_messages] view instead for these cases.
In our home made monitoring system we're checking the subsystem in sysjobsteps, then use the command from there to identify the dtsx package name and looking up the latest message from [SSISDB].[catalog].[event_messages] for that package for the error message.
21 votes -
non sql servers should not need a license
i think it would be very nice being able to have alerts for non sql servers without the need to allocate a license to those.
3 votes -
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 -
add user editable notes in estate
Add the ability to add some basic text notes for each instance that can be viewed in the estate view. Want to keep some basic notes such as purpose of instance, application server dependencies, etc. Currently use external document to keep track of these.
2 votes -
Share alerts via Email
The ability to share alerts details via Email from the "Alert Details" page.
Sometimes we don't want to share a direct link to the monitor.
E.G
Click "share" which will open a mailto: with the relevant alert details.1 vote -
1 vote
-
Be able to schedule a maintenance window with the possibility to use an offset.
Be able to schedule a maintenance window with the possibility to use an offset. Say every 3rd tuesday of the month + 12 days.
5 votes -
Summary alert page ordered by active alert type with drill down to detail
In the previous red gate alert program it had a summary by each alert giving a quantity for the selected monitor period and one could then drill down to the detail for that specific alert in chronological order starting with the most recent - found this most useful - also gave a simple measure of occurrences over time which one could use to track the effectiveness of efficiency projects
2 votesThanks for the suggestion – we believe this has been addressed with the Grouped Alerts released in Version 7.1.18.
We will close this suggestion, but please do raise another suggestion if you have other specific improvements you’d like to see.
Kind regards,
Adam
SQL Monitor Development Team -
Disable specific alert for some time
Make it possible to ignore a specific alert for a specific server for x amount of time. Sometimes there is something going on for say half a day and you do not want to miss out on other errors but just that specific one.
2 votes -
see sessions from sys.dm_exec_requests in top 10 queries
I never see commands like BACKUP DATABASE or ALTER INDEX in top 10 queries and got the message from support that the information is taken from sys.dmexecquerystats
As it is now it is hard to track down where heavy I/O comes from if it is for example index maintenance or backup.
I think RedGate should record all commands from sys.dmexec_requests and join in the execution plans where they exist and other stats if needed17 votes -
Allow Fractional Alert Thresholds.
When you use the "Calculated rate of change" functionality on a custom metric, the results come back in fractional values and you should be able to alert on these values. In my case, I want to monitor number of orders for the last 10 minutes. There are always relatively few orders at night and many during the day, but if order flow drops off drastically in a short period of time, I want to know about it.
Unfortunately, I can't just alert when the rate of change drops by 25% (-.25) because alerts can only happen on integer values. 100%…
4 votes
Daniel Rothig
responded
A current workaround is to multiply the result by a factor, eg. 100 to make the result a percentage.
-
Have database sessions displayed with the networking info from sys.dm_exec_connections(SqlServer)
Having a window of session connection information, especially using the network info per session as seen in the sys.dmexecconnections view from SqlServer would be very helpful. This also helps in associating network latency waits with the actual app session(s).
4 votes -
Exclude a database, instance or the entire alert based on an actual alert
It would be a nice feature to be able to click on an alert and get the option to exclude future alerts:
1 - for this specific database
2 - for this specific instance
3 - for this specific alert3 votes -
be able to set top level notification settings through powershell module
I want to be able to use Redgatesqm.ps1 to configure smtp server, default email list and other top level notification options.
1 vote -
deadlock Detailed Report
Please create a detailed deadlock report.
In addition to the existing DeadLock summary report, can you please create a DeadLock Detailed report for all deadlocks for a given time range.
Looking for a DETAILED report of deadlocks (all deadlocks for the time range) that will include:
1. Date / Time of the event
2. Blocking SPID and full query text
3. Duration of the block
3. All Child or deadlock victim SPID and full query text of the victim
Similar to the summary report, will need to be able to select the SQL server instance and / or database to…3 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 votesAs of v14.0.23 (September 4th)
We have Redesigned of the 'Alert History' and 'Occurrences' tab in the alert details page. This combines them into one tab and allows for easier access to previous comments.
- Don't see your idea?