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.
710 results found
-
Add the ability to report/analyize Index fragmentation
I would love to see the ability to see the Index Fragmention results in the report/anayize feature. I have been fighting index fragmention but cant really tell how much it has improved.
9 votes -
Add filtering to the Top 10 Queries/Waits lists
So first, this is a request for more general filtering than the 2 requests I see already exist for filtering by database (which I believe you can get to by clicking the database name further down the page, but would certainly be more convenient on the top 10 lists directly).
The primary use case that I was looking to do but couldn't was sort by averages, but set a minimum execution count. The goal being to find my worst queries that are not just one off things that aren't likely to be repeated. I think there would be a LOT…
9 votes -
We would like to send slack messages to different channels depending on the server.
We have multiple teams who are ultimately interested in what is wrong with their platform, The posting to a single slack channel is good, however giving an option to send only messages from certain servers to specific channels would improve our customer engagement. currently the main channel is ignored by the all teams except the dba's as the chaff from other servers can cause disinterest, or interest when no reason for a team to investigate.
9 votes -
Database Tags
It would be great if, in addition to Instance Tags, we could assign tags to individual Databases as well. This could help in various ways in trying to determine what the purpose is of the vast number of databases we need to monitor and manage.
9 votes -
Ability to add notes to tracked queries
When working in an environment with multiple people is typical that each person is tracking different queries to analyse ongoing changes/improvements.
Being able to note something as "Tracked by Cláudio. Following FIX #1234" would be great.
It will give us a clue on who is working on what and reach out to that person. Or just keep small notes during the analyses.
9 votesA great suggestion. We are exploring this as part of a wider review into improving query tuning features.
-
Webhook Filter on Alert Severtiy
Situation: After setting up a webhook of SQL Monitor to Service Now we are getting tickets of all priorities
Background: We would only like tickets to be created that are actionable
Assessment: We can enable this on the javascript side of the service now webhook to remove low priority webhook calls however it would be prefered to do it in RedGate
Recommendation: Is it possible to have the same feature that email has "Call webhooks only if alert severity is High or Medium only"
9 votes -
Alert "regarding "instance alerts" - Cluster failover - for Postgres"
for Alert "regarding "instance alerts" - Cluster failover - for Postgres", would like to have it available on the individual server level and not just the monitoring group. That way we can customize our notification accordingly.
9 votes -
Have a standard metric for Data space used
There is currently an out of the box metric or Log Space Used, but there isn't an equivalent Data Space Used.
I get that it's a bit trickier if you have multiple data files, (even just adding them up as one metric). We have databases that we want to pro-actively allocate space for but it's hard to do without a metric to tell us when it's getting full.
8 votes -
Configurable Thresholds Based on Time
The alerts would be more useful if we could apply maintenance or quiet periods to them.
I understand we have the maintenance window and that is perfect for things like planned downtime, index maintenance etc.
Regards,
CliveHowever, the issue I currently face is that I suppress the processor under utilised message. Like a prolonged spike in CPU activity, a massive drop off could be a concern too. However, I have a current mean of 18.6% on one example server. I can set a threshold of 15% as an example, but this would trigger alerts through the night when typically…
8 votes -
Include Custom SQL Code in alerts
When creating custom alerts, I would like to be able to include information that can be retrieved by running a SQL query.
One example is using the pre-built Failed SQL login custom alert that is available to setup. The alert notifies when this event occurs, but it fails to include information like which login failed, etc.
It would be nice to be able to build part of the e-mail body in the alert to include some critical data that can be queries using T-SQL.
8 votes -
Select what alerts i want to receive by Slack, the same way it happens by Email
Slack messages are a little annoying when all the alerts are sent by them.
I would like to configure the alerts i want to receive on slack. Today this is possible to configure in the e-mail option.8 votes -
Improve alert troubleshooting by showing sql server error log
When viewing an alert it may be helpful to see the error log for the server for the surrounding time. RAISERROR can log to the error log, so this info could be useful to see.
8 votes -
Job execution in overview graphs
It would be nice if you in the Overview graphs could see SQL Agent Jobs, just like long running queries, deadlocks etc.
It could be good for troubleshooting high disk IO, CPU etc, if you could see that a job has started running at a point.I've tried to illustrate my idea in the attached file.
8 votes -
be able to show basic SSIS monitoring graphs/sparklines on the overview page (Buffers spooled, Buffers in memory, rows read,...).
There is currently no SSIS monitoring in SQL Monitor. You can add custom metrics for performance counters available through SSISDB but these can only be seen on the Analysis page and only after you have selected all of them.
It would be nice to be able to select SSIS as an option for a server and then see these counters as graphs/sparklines on the overview page.
8 votes -
Comments in alerts list
Show the comments or at least the first 50 symbols of a comments in the Alerts list.
8 votes -
Add ability to search Server Log
I would like the ability to search the error log or at least filter out some alerts. For example, we get about 45 "Log has been backed up" log entries every 15 minutes. It's very hard to actually find things on redgate without having to login to the SQL server and filter there.
8 votes -
export the overview page
The reporting is very limited and provides less detail that the overview and estate pages. We need to be able to export the overview and estate pages easily. Also need to be able to report on the Top queries and top waits.
8 votes -
Slack notification in more detailed
Slack notifies the alert, would be great to view complete details in slack specific to notified. This helps giving access to development for a slack channel to look into Long Running Query corresponding to database. without giving full access
8 votes -
Have the option to capture parameters from queries
Presumably this would require having the trace enabled and you wouldn't necessarily want to be capturing every parameter on every query so there probably needs to be some logic around choosing what to keep. This would obviously help track down parameter sniffing problems along with other troubleshooting of the exact scenario you are trying to look at.
This is different from the suggestion listed here:
https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/41237467-display-parameter-list-in-the-query-plan-form(And that one should also be implemented and would be a valuable time saver)
8 votes -
Detailed Memory usage breakdown
I would like to see a breakdown of memory usage. For example, how much memory is used by the plan cache, how much for the buffer pool, etc.
Also, a breakdown of memory usage per database.8 votes
- Don't see your idea?