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.

  • or

747 results found

  1. Prevent Active Directory lockout from a single failed attempt to log into the dashboard

    If the user mistypes their password when trying to log into the SQL Monitor dashboard, their Windows account gets locked out in Active Directory. This happens on the first failed attempt, so presumably there's an automatic retry happening.

    (This ticket is similar to https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/16845169-keep-from-locking-account-when-registering-server, but that one is for the server monitor login and this is for the dashboard user's personal login)

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Improved windows range handling for Individual query monitoring

    The current windows range on the new Query executions tab is fixed to 2 hours. Should be great if the length of the windows range could be customised.

    At the same time make it working together with the zoom range on the History tab. This so if you have zoomed in to a certain time range on history tab then when opening Query executions the same time range should be used as the windows range. Alternatively you could use the same type of windows range and zoom range that are already used on the History tab.

    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…)
    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)
    Close
    Close

  3. Make alert configuration levels more discoverable

    CONTEXT: In SQL Monitor, you can configure alert behaviour down to the object level (such as the Database or the Job level). This is useful e.g. when we have specific databases with different backup policies to our global configuration, since we can specifiy "special rules" for individual databases.

    PROBLEM: It is counterintuitive how to do so, and many people don't spot the left-hand drilldown navigation - this makes you think that you can only configure on the global and the server level! Also, when we have created an override, it's easy to forget so causes surprise when we…

    180 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…)
    42 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)
    Close
    Close

  4. 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 →

  5. Print the server overview

    Print the server overview (scroll) to share with team members to assist in correction of failures.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. AWS FSx drive status

    In our company we are using AWS FSx drives for our SQL Server databases. The FSx drives are not real drives, they are more like a shared folder, I'm wondering if there is a way to add those drives on SQL Monitor so we can check disk space and get alerts. AWS has been adding more features for FSx drives to be used on SQL Servers. Right now the only way to monitor that is using AWS console or alerts, which are not very friendly and only available for some system administrators.

    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…)
    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)
    Close
    Close

  7. SQL Monitor currently does not have customization on scheduling for custom metrics

    SQL Monitor currently does not have customization on scheduling for custom metrics- only per min\5 min\hour basis.
    the option to setup your own schedule could be given to users and setup your own frequency or metric collection.

    15 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Licensing Clusters

    Since only one SQL server is active in an Active\Passive cluster, you should not require multiple Monitor licenses.

    50 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  ·  Daniel Rothig responded

    Currently, we are offering a 50% discount for passive cluster nodes. We’ll continue to review our pricing structure over time.

    Why do we charge money for passive nodes at all? Covering your passive nodes with monitoring is necessary to ensure that when a failover occurs, the passive node is in a healthy state, and the failover will be able to succeed. However, passive nodes don’t (usually) have complex performance characteristics, hence the discount.

  9. Enhancement Request – SQL Server Licensing Page

    The SQL Server Licensing page should take into account the licensing model of monitored SQL Server instances. For example, Azure SQL Server VMs running under a Pay-As-You-Go licensing model should be identified and optionally excluded from the license requirement calculations.

    If the purpose of the page is to help customers understand how many SQL Server licenses they need to purchase or maintain, consumption-based instances should be clearly highlighted and treated differently from instances covered by traditional licensing.

    Otherwise, the licensing figures may be misleading, as Pay-As-You-Go workloads do not contribute to the customer's on-premises or bring-your-own-license requirements. Adding this…

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. we dont allow ping to cross vlans so i cannot add servers to monitor

    we dont allow ping to cross vlans so i cannot add servers to monitor

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Feasibility of selecting databases across the sql instances to create custom metrics

    Imagine we are planning to create a new custom metric which we wish to use across several instances but one specific set of databases. its currently impossible and will be one to have.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Control Alerts Using Metadata

    CONTEXT: We have a maintenance and backup solution which uses SQL Server as a backend to determine what databases to perform the tasks against, and at what time.

    PROBLEM: Some databases do not have maintenance tasks running against them, but still have alerts which appear in SQL Monitor for them (e.g. Index Fragmentation). I don't want to manually exclude these from SQL Monitor, as the number of databases fluctuates, particularly on our testing and development environments.

    EXAMPLE SOLUTIONS:
    - Provide a means of easily enabling/disabling/changing alerts dynamically using a stored procedure.

    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…)
    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)
    Close
    Close
    Daniel Rothig responded

    For your usecase I recommend modifying the maintenance window metadata instead:

    UPDATE s SET MW_IsEnabled = 1, —or 0 to enable alerts again MW_Start=0, —midnight MW_Duration=864000000000, —24 hours MW_Monday = 1, MW_Tuesday =1, MW_Wednesday=1, MW_Thursday=1, MW_Friday=1, MW_Saturday=1, MW_Sunday=1 FROM [settings].[SqlServers] s INNER JOIN [settings].[Clusters] c ON c.Id = s.ParentId WHERE c.Name = ‘hostname’ AND s.Name = ’’ —Set to SQL Server name or leave empty for unnamed instances

    A restart of the base monitor service will be required after the change

  13. Possible AI usage for Alerts in Red Gate Monitor

    The alert system for Red Gate Monitor could be improved with some more intelligence. For example Full backup jobs and differential backups, weekly full, daily differential. Of course the differential will take a lot more time just before the full backup in comparison with the differential backup just after the full backup. If Monitor could "learn" the environment and only give alerts when things are really off then this would be much better.

    5 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. SQLMonitor consider the SQL Server cluster name as an instance

    SQLMonitor consider the SQL Server cluster name as an instance

    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…)
    4 comments  ·  Admin →
    completed  ·  Neil Turner responded

    This can be set within Display settings ('Failover Cluster Name Display') for a SQL Monitor configuration.

  15. add LDAP/NTLM authentication so that Windows domain users can log in as themselves

    That's it, really - configure read-only/read-write access via Active Directory group memberships or user lists built into SQL Monitor, and allow individual users to log in using their own AD credentials.

    142 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…)
    10 comments  ·  Admin →
    completed  ·  Daniel Rothig responded

    SQL Monitor 5.0 lets you log in with your AD credentails. Admins can configure individuals or AD groups to have access to SQL Monitor, and have granular access control over which servers users can see.

  16. Custom Metrics are specific to a base monitor without a way to copy them

    I have to create all custom metrics and alerts 3 times, once in each base monitor. And there is no way in the UI to copy from one to another.

    I guess this makes sense because each base monitor only knows about the groups and targets it has. But it would be a great enhancement if the UI supported copying the custom metrics from one base monitor to another.

    5 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Report showing least or busiest server.

    I would like a report that uses the historical data collected by SQL Monitor that would show the least busy or busiest servers so that I will be able to plan where to put additional workload, or re-distribute work load.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. Integrate query store with monitor to find regressed queries

    Query store already tracks regressed queries. Integrating this into the monitor and having the ability to alert on this would be extremely useful in having early notifications on when a query goes bad before application or system issues come up

    5 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Custom reports against alerts, queries and metrics

    CONTEXT: We want to see the bigger picture arising from the data presented in SQL Monitor.

    PROBLEM: Currently you can't pull together a report in the SQL Monitor UI, and the monitoring database is not particularly accessible. We need reports against:
    - The metrics shown in the analysis graph
    - The top queries and waits
    - The alerts raised over time
    - Server configuration and SLA

    EXAMPLE SOLUTIONS:
    - Provide reporting scripts against the monitoring database
    - Privide a BI interface against the monitoring database
    - Priovide richer data-export functionality in the UI
    - Provide a…

    263 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  ·  56 comments  ·  Admin →

  20. Connect to Azure database via express route

    Currently I'm only able to connect to Azure SQL Server (PaaS) via internet and URL servername.database.windows.net.

    We have a direct connection to our Azure environment via Express Route. Therefore I want to use this also for the monitoring, but per default SQL Monitor uses external URL.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 … 6 8 10 … 37 38
  • Don't see your idea?

Suggestions

Categories