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.
718 results found
-
6 votes
-
Add development machines without a license.
You should be able to add development machines at no additional cost if you already have a production license. If you do not have a license for the development instance then the features can be scaled back to only allow you to view alerts.
35 votes -
Correct Database file usage alerts with In-Memory/Filestream Filegroups
The Database file usage alerts in V 8.2 are great, however they do not work correctly with Filestream filegroups. per https://forum.red-gate.com/discussion/comment/153592 they are not supported.
Please either add support for these filegroup types or disable them by default so we are not spammed by alerts for something that's not valid.
Thanks,
-Luke.6 votes -
Stop being nagged about maintenance windows - because they don't fit our operation
We don't have regular maintenance windows. Getting a nagging remainder about setting maintenance windows every login is very annoying. I'm currently running SQL Monitor 8.0.16.15996.
Yes, I know that this has been raised before but that particular question has been "closed".
4 votes -
See who is using SQL monitor
Before I upgrade SQL Monitor I'd like to see who is logged in/using it so I can inform them.
2 votes -
Remove dropped database from Configuration>Monitored servers
I would like to be able to delete a database from Configuration>Monitored servers, if that database has been dropped from the monitored SQL server.
As it stands now, if a database has been dropped, I have to remove it manually from the RedGateSQLMonitor database via script.6 votes -
Allow maximum number of email notifications in a 24-hour period alert to be sent to another email address
Currently if too many alerts for a particular object are received an alert email is sent noting that no more emails will be sent. I want to be able to specify that email is sent to a different address than the default.
For example, we may get a large number of deadlocks. after the first 150 the alert emails are silenced. We configure deadlock alerts go to our normal email address because generally they aren't urgent, however when 150 or more are received there is a definite problem that needs to be reviewed. That should go to our pager email…
9 votes -
Be able to set an Alert to escalate when it has been active for a certain amount of time.
I have a several different Jobs that fail periodically, once in a while is not a big problem but when they continue to fail over a period of time it does become a problem and I need to know. Likewise when I have an AG is slow to sync in the middle of the night when it is rebuilding all of the indexes of a 1.2TB database and syncing across to locations in 2 states I don't want to be paged, but if it is persistent through the day I do.
1 vote -
Export options for "Head Blocker" diagram
The "Overviews | BLOCKING PROCESSES (TOP 10 BY TIME)" shows a really nice chart of the blocking chain. It would be useful if this could be exported to an image file and/or a CSV.
22 votes -
Group alerts into a hierarchy
I want to be able to group alerts into a hierarchy so that for instance when a server goes offline, all of the other alerts generated such as instance unavailable are not generated.
3 votes -
Display on TV screen
Hi, We run Yodeck boxes to display content on TV's
This has a scripting function to pass some logon details
It would be good if I could have a read only view of the server dashboard or help identify the submit button to script it
Ive tried - Only the password is enteredtype("""#password""","""MYPASSWORD""")
click("""#remember-password""")
click("""#submit""")4 votes -
I would like to be able to install an update without having to change the browser port.
I start with port 8080, when installing an update the port is "in-use" so I have to switch to port 8081, with the next update I switch back to port 8080.
Surely the update should be smart enough to see there is a running process and either disable the web process until the update is finished, or make the update without having to change the port1 vote -
Execute an action when a custom metric alert is rising
It would be helpful when you could pin an action to a custom metric alert.
4 votes -
Be able to report on current alert configuration at All Servers and Specific Servers/Instance levels
Be able to run a report or create an output file that lists default and customized alert settings at All Server, Server and Instance level (Including notification setup).
This is a common request from management and at this point the only option I can think is to setup a spreadsheet and start going through all the alerts.
1 vote -
Sortable columns on the Alert Inbox (Grouped or ungrouped)
The Alert inbox should be sortable by column.
It would be much easier to focus on key items if the Alert Text column could be sorted. A straight alpha sort (Asc or Desc) would be great. So for instance a "Long-running query (731)" would sort before a "Long-running query (525)" and all of the "Long-running query" be easy to seledt and clear.2 votes -
Provide a direct link to the base monitor download
When installing updates, only the SQL Monitor web service link is initially provided. In order to get access to the SQL Monitor base monitor download one has to first install the the SQL Monitor web service. This process slows down upgrade time and extends the "broken state" time in a multi-base monitor configuration.
Please provide a direct link to the base monitor download without requiring an initial WebService monitor install.
4 votes -
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 -
Showing Unlicensed and will not allow you to stop monitoring
I added a server that I needed to monitor for a couple hours. When I was done, I swapped out the license and attempted to pause the monitoring to remove the blue banner at the top:
You have unlicensed servers. Unlicensed servers will not be monitored and will not raise alerts.
However, I was unable to pause the monitoring as it just refreshed the page, with the blue bar at the top, and the "pause monitoring" button still enabled and "resume monitoring" button still disabled. Ideally, there would be a way to say I don't want to monitor this server…
4 votes -
Alerts for suspect_pages
We would like to see alerts for suspected pages.
Errors Recorded in suspect_pages Table
The suspectpages table contains one row per page that failed with an 824 error, up to a limit of 1,000 rows. The following table shows errors logged in the eventtype column of the suspect_pages table.
Error description eventtype value
823 error caused by an operating system CRC error or 824 error other than a bad checksum or a torn page (for example, a bad page ID) 1
Bad checksum 2
Torn page 3
Restored (The page was restored after it was marked bad)…17 votes -
Analysis graph exclude set times over long time range such as 28 days
It would be great to be able to set exclusion times such as the "maintenance windows" when index maintenance activities take place such as every day between 12pm-2am in our case. During these times disk queue length will be predictably high due to the maintenance activities taking place.
When viewing graph analysis for a 28 day period for disk queue length you see peaks which are from the maintenance activities and these events end up skewing the overview of BAU activity.
It would be great to be able to define an "exclusion time window" in the analysis report window to…14 votes
- Don't see your idea?