Skip to content

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

756 results found

  1. Long-running query Alert - time based parameters

    I need to disable monitoring long running queries at night.
    My proposal is that you could add new parameter to alerts
    Time from - Time to which will exclude monitoring during this time.

    That will help to exclude ETL - ssis, and other long rununig queries which we set up at night.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. silence alerts for x hours

    If an alert is firing repetitively for say a job failure, to be able to silence the alert for a number of specified hours (not permanently) if you know it will recover later, but you don't want to disable the job - just want the alerts to stop temporarily

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Improved view of User Sessions

    Visibility into user sessions could be improved. The current list on the instance overview, "SQL User Processes (Top 10)", is a start but needs the following to make it useful:

    1) Don't limit the number of sessions shown; rather add paging controls like on the error log view, so that it would be possible to see any session for any selected time period
    2) Add a columns for:
    - Login (i.e. login name)
    - Blocked by session Id (maybe even an icon if a session is blocking/blocked?)
    3) Make it possible to sort by any column
    4) Add ability to…

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Availability Group alert details

    It would be great to see the server name in the mail body which is affected by the alert. Currently it is only in the subject. EG: Raised on detail i the mail body contains the primary replica, the affected unreachable replica is only in the subject.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. occurrences

    Please retain a "tombstone" that can be referenced to present a history of "Occurrences" for HIGH Alerts. Allow us an additional retention period so these don't hang around forever - but please don't limit the number of days, just a smallint would be good.

    When Monitoring Fails and is cleared, the Occurrence disappears when DB maint nukes "old cleared Alerts". If the retention period is short, say 14 days, the history of occurrences is soon lost.

    A "tombstone" would at least keep the occurrences for trending.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Daniel Rothig responded

    Just keep the alert data in the Purge settings indefinitely – it’s only the metadata of the alerts, none of the performance data, so are “tombstones” as you described

  6. Notification

    Generate Notification Per Alert (optional) and Show in windows
    when Browser is Close.
    And then Send Text Message To User Mobile Number

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Collect SQLServer:Memory Manager counters.

    This would be especially useful for SQL 2012 where counters have been removed from the buffer manager exist in the memory manager counters. For SQL Server 2012, I have observed that there is a memory leak and this is revealed by observing the Memory Manager Optimizer Memory (KB) counter.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Daniel Rothig responded

    Hi, we’re monitoring a few of those out of the box and the rest can be covered via the custom metrics feature – check out sys.dm_os_performance_counters

  8. Add Text Boxes/Areas to Reports

    I have reports that I circulate from SQL Monitor. I have to edit these before I issue them to add additional information. E.g. Under the "Lock Waits/Sec" chart I have a description of what a "Lock Wait" is, what impact it has, what's an acceptable value, etc. I tried supplying a supplementary sheet with this info but the management team prefer it under each chart / metric.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add an index to Alert.Alert on AlertType to remove index scan

    Here's the index. It really helped speed up the system (monitoring 20 servers)

    USE [RedGateMonitor]
    GO
    CREATE NONCLUSTERED INDEX [AlertType]
    ON [alert].[Alert] ([AlertType])
    INCLUDE ([AlertId])
    GO

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. ignore events triggered from SIEM vulnerability scanners..

    when we run a vulnerability scan on our SQL servers we get a lot of redgate alerts, i know you can setup to ignore certain alerts and have a maintenance window but ignoring the alerts isn't an option (what if its actually a hack) and the maintenance window is dangerous for obvious reasons.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. see an administrative web-based log viewer

    Having the ability to review logs in a web-based interface is useful for administrators of a tool so we can diagnose and remedy some problems without needing to reach out to support. The downside is the log needs to be filterable or multiple log files need to exist.
    An example of a log that would be useful would be an email log. In the event an email fails to send, I'd like to know why without needing to download the entire log in a zip, extract the zip locally, and browse through it when I am looking for a specific…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Be alerted when a database approaches it's maxiumum file size

    Whether or not autogrowth is enabled, I'd like to be alerted when a database approaches it's maximum file size.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Being able to filter "TOP Queries" by any of the columns

    On the "TOP Queries" grid we can order it by any of the columns (besides "Database").

    I would like to be able to filter the rows by the amounts.

    Example:
    Filter queries where "Execution count > 100" same for other columns.
    Then apply the "order by".

    This way we can filter together with the "Enter search term" box.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Remove single AG replica

    Currently when adding an Availability Group it automatically discover and add all replicas which is great.

    However sometime we might not want all replicas to be monitored, in our case it's because of limited bandwidth on a certain asynchronous node. While it is indeed possible to "Pause Monitoring" on that node, it would be nice to be able to delete it completely (using some kind of exception list so it's not re-added automatically).

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Filter for Database with no Tlog backup

    On the Estate->Backup page, it would be great to have an additional drop-down option for 'DBs without Tlog"

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Additional Overview Tab Suggestions

    • OS configuration (how many sockets/cores and Memory are allocated) * SQL Server, Mongo and PostgresSQL environments Right now there are only %’s, I want to see of what.

    • MongoDB Memory configuration I see SQLs but Mongo is missing. i.e. WiredTiger Cache settings

    • ReplicaSet information for Mongo, along with who is the primary, secondaries and where are the secondaries seeding from, and the status.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Grant user access down to SQL instance or database level

    Currently the lowest level we can grant users access to cluster level. In multi-instance clusters this gives too much. Need to scope user access to instance and database level.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. More options for Custom Metric Frequency

    Would it be possible to have a custom option for the Custom metric gathering, as it stands the data can be collected at intervals of 1,5,10,30,60,1440 minutes

    it would be nice to be able to select a custom value and values less than a minute, the standard metrics that are gathered appear to be gathered every 20 seconds which isn't an option here

    Thanks for your time and concideration
    Ste

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Daniel Rothig responded

    Note that you can currently hack an arbitrary “seconds” value into the SQL Monitor database – but changing the Custom metric configuration via the UI will reset the collection interval to one of the default values.

  19. Blocking process Hover Information should show Total Blocking Duration

    The (Restored in 8.0.6) hover over the Alert List's "Last Updated" column shows the duration of the Alert itself, NOT the total time involved.

    Unless you memorize the configuration of this Alert for each of its 3 severity levels, and assume they never change, and never vary by server, nor by database... you must sill open each event to see the "Total blocking duration for all descendants" published under the "Details" tab, then add that to the event duration, for which you must now do time subtraction as there is no "Duration" on the Status line... (another omission).

    Having…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Display running SQL text instead of full batch

    Hi Team,

    Currently, Active Sessions displays the full batch text instead of the exact running SQL statement. It would be significantly more valuable to show the specific executing query text.

    Having immediate visibility into the exact query would allow us to quickly identify blocking, long-running, or resource-intensive statements without relying on additional tools or manual investigation. This would reduce troubleshooting time, speed up incident response, and improve overall performance monitoring efficiency.

    I believe this enhancement would provide clear operational benefits for teams managing busy production environments. Thank you for considering it.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Suggestions

Categories