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.


In Redgate Monitor, I want to...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

218 results found

  1. Recognize Low Alerts visually in overview

    Low Alerts show as blue dots on the Latest Alerts panel, but in the overview they show Green like Healthy.
    Especially when showing Small Tiles (we monitor 60+ instances) they do not stand out from Healty ones (see the attached examples).

    For that reason I dont use many Low Alerts.
    It would be more consistent to use blue in the overviews also.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →

  2. search Top Queries

    I have a process that reports on stored proc outliers. When I go to SQL Monitor, it is very difficult to search the top queries to find the particular stored proc.

    For instance, if I do a ctrl+f and search for "I.Invoices", the search may find that snippet in "hidden" areas (in the dropdowns) but I cannot tell where the found items are.

    A query syntax search of the top queries would be extremely helpful.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  3. Job Duration Unusual: Threshold higher than 100%

    Currently when configuring different threshold in the "Job Duration Unusual" alert we are limited to a maximum of 100% of the baseline. So for example if I wanted an High alert when a job is 5 times the baseline it's not currently possible, I'm limited to 2x.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  4. Show Job name instead of ID in query related alerts

    This is a follow-up on: https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/1865305-show-job-name-not-job-id-value-for-job-related-ale

    The job ID was replaced by the job name in Job Failing, Job Duration, Job Cancelled alerts but I would like to see the same for query related alerts, specifically Long-Running query but the comments in the other item also mention Block Process and Deadlocks.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  5. See on the overview page incase of a AlwaysOn or a windows cluster which node is the active\primary

    We have several windows clusters and AlwaysOn clusters. It would be very helpful to see on the overview page which node is active.

    It can be easily done by adding a color to the AG icon on the tile.

    I know that it can be seen on the cluster overview but I really think it belongs on the Overview page.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →

  6. Ability To Alias PaaS (SQL Azure) Instances

    You currently can alias IaaS instances but the option does not show up if it is a PaaS instance.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  7. Monitor Azure Managed Instances

    Redgate Monitor still does not appear to fully support Azure Managed Instances. As our primary business is about to move across solely to Azure Managed Instances, this is now a seriously high priority for us.

    We are heavy users of Redgate Monitor for our business, so this is now starting to be become a bit of a worry for us.

    46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  8. Wire up Notifications to MS Teams (in addition to Slack)

    Wire up Notifications to MS Teams (in addition to Slack)

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  9. Don't check Agent status for Express Edition

    Whenever I add a server to the monitoring that is Express Edition, I get alerted that the SQL Agent service is not running.
    Well d'uh. It's Express Edition. The Agent service cannot run on it.

    Instead of always giving me this alert and then having me go in and disable it for yet another server, why not change the logic to not raise this alert at all when the edition is detected as Express?

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  10. Commit to supporting Linux in some way

    Linux is the future of sql server. If you've not deployed SQL 2019 AlwaysOn on Kubernetes I'd highly suggest you do. The install is lightning fast compared to clunky Windows installers of the past. I really feel like Redgate is taking a slow poison by not getting on this sooner. Honestly most of the metrics in sql monitor come from the internals of sql. All we really need from Linux is probably free disk space and cpu.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Admin →

  11. Add 2017 CU14 to Estate view

    Currently SQL Monitor shows the latest SQL Server 2017 version to be CU13 yet the latest is CU14. This should show the latest version.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  12. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →
    completed  ·  Adam responded

    Thanks 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

  13. In the Estate view you are 2 CU's behind for SQL Server 2016.

    Currently SQL Monitor shows the latest SQL Server 2016 version to be SP2 CU4 yet the latest is SP2 CU6. This should show the latest version.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →

  14. Support SAML for Web Single Sign-On (SSO)

    SQL Monitor should be able to support Enterprise Single Sign-On using SAML. Is this on the roadmap?

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Admin →

  15. Have more flexibility in Maintenance Window Schedules

    We do OS and SQL Server patching one Sunday a month for dev and QA and the following Sunday for production. I think if maintenance windows scheduler looked more like setting a schedule in an agent job it would be perfect for setting these kinds of maintenance windows. And if we could drive setting / modifying maintenance windows via T-SQL that would be even better.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    completed  ·  Neil Turner responded

    Thanks for this suggestion. SQL Monitor 10 now allows teams to suppress alerts, or just their notifications, over certain periods using alert suppression windows. Please see What’s New in SQL Monitor 10 for more details (https://www.red-gate.com/hub/product-learning/sql-monitor/whats-new-in-sql-monitor-10).

    We hope this meets requirements and will mark it as completed. Please raise further suggestions for any improvements you would like to see.

    Thanks,

    SQL Monitor product team

  16. suppress emails during maintenance window

    Allow the ability to suppress all alert emails during a maintenance window. Right now we have ~65 SQL servers and during windows when the OS team is patching and rebooting the servers we can receive 100's of emails as the servers go up and down. It would be great if we could set a schedule or at the very least a single use window when emails don't get sent.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    completed  ·  Neil Turner responded

    Thanks for this suggestion. SQL Monitor 10 now allows teams to suppress alerts, or just their notifications, over certain periods using alert suppression windows. Please see What’s New in SQL Monitor 10 for more details (https://www.red-gate.com/hub/product-learning/sql-monitor/whats-new-in-sql-monitor-10).

    We hope this meets requirements and will mark it as completed. Please raise further suggestions for any improvements you would like to see.

    Thanks,

    SQL Monitor product team

  17. Read Only users should not view Analysis page.

    When restricting "Read Only" users they can still see all servers when viewing the "Analysis" page. I think this should also exclude any servers not explicitly defined in the Managed Users page.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    completed  ·  Adam responded

    Thanks for this suggestion. This has been fixed in Version 9.0.6 (although I would suggest updating to the most recent version, v9.0.7 at time of writing) when we fixed the issue SRP-11791: AD user can see names of servers they don’t have access to fixed for Analysis and Backups.

    Hopefully this completes this suggestion.

    Thanks,
    SQL Monitor Development Team

  18. Hide Nonrelevant Metrics

    The addition of Azure metrics has made the selection of metrics within the analysis page less efficient; as there are now twice as many items to pick from, many with the exact same name. In my environment, there are no Azure databases being monitored, so these metrics only serve as a clutter. It would be nice if metrics were hidden that aren't applicable to the list of monitoring SQL Servers.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  4 comments  ·  Admin →

  19. Remove wait type VDI_CLIENT_OTHER from the wait graph

    SQL Monitor shows high waits for SQL Server 2016+ systems that implement availability groups configured for automatic seeding. Since a multiple system processes called VDICLIENTWORKER are left running by design. This wait tends to be the top wait in an AG configuration and erroneously indicates a problem that does not really exist.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  20. Monitor SQL instances running in AWS RDS

    Enable SQL Monitor to add AWS RDS instances as monitored servers

    101 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Admin →
2 4 5 … 10 11
  • Don't see your idea?

Suggestions

Categories

Feedback and Knowledge Base

(thinking…)