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.

240 results found

  1. Multiple Maintenance Windows

    I would like to be able to set two maintenace windows every day.

    98 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…)
    14 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. Multiple windows can be set-up. 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

  2. Do other tasks than send email on new alert

    It would be nice if it was possible to allow other tasks when a alert is raised. Other tasks which could be called: Script file, url, exe file.

    96 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  ·  19 comments  ·  Admin →

  3. Reduce the number of false-positive status alerts (e.g. Machine unreachable)

    CONTEXT: Many status alerts (eg. Machine unreachable) have a simple configuration model, meaning that these alerts will trigger as soon as a ping to the Machine fails.

    PROBLEM: VPN connection resets, scheduled restarts, etc. all may be acceptable causes for a ping to fail in our system, but these currently lead to a lot of false positives... provided they are brief, and the system recovers in time.

    EXAMPLE SOLUTIONS:
    • Add configuration to the machine unreachable alerts to set a time threshold
    • Require two consecutive pings to fail before raising the alert

    92 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…)
    15 comments  ·  Admin →
    completed  ·  Adam responded

    Version 5.0.5 introduced the ability to configure machine unreachable, and SQL Server instance unreachable, by multiple time thresholds. We left this open for a while to see if there were any further requests. Thanks for the suggestion.

  4. Increase user granularity and allow creating more than the 3 built in user accounts.

    Increase user granularity and allow creating more than the 3 built in user accounts. For example, we have an offshore development team that would like access to their SQL instance, but can’t have access to any other instances. What I would like to do is to be able to create an account, assign permissions to that account against databases or instances, limiting the access they have to production systems. If we could get it to use AD integration rather than forms authentication as well as being able to set permissions granularly then that would be ideal.

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

    SQL Monitor 5.0 introduces Active Directory integration with granular control over which user sees what. Please note that you will need to enable Active Directory authentication in order to make use of this functionality

  5. Identify head blocker in a blocking chain

    It would be quite useful and timesaving if one could identify the head blocker for a blocked process (as done in SSMS's Activity Monitor, Processes tab). Otherwise when get a lot of blocked process alerts, you have to manually figure out the head blocker by analysing all the alerts.

    79 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 →
    completed  ·  Adam responded

    This work was completed in version 5 – apologies for the delay in updating.

    If you view a “Blocking process” alert, clicking on the ‘Processes’ tab (next to the details tab) will show the head blocking process, followed by any blocked processes.

    If this doesn’t meet your requirements, please let us know how we can improve this alert.

    Kind regards
    Adam

  6. Specify a "details" query for custom metric

    When I define a custom metric it would be super-helpful to be able to see some details that gave rise to the metric value. For example, I have one for "count of failed SQL logins in the last 10 mins". But to find out which logins failed, I have to go run queries in SSMS.

    I'd like to be able to define a "details" query on the custom metric, the results of which are captured at time of collection, and are then available from the alert.

    76 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…)
    8 comments  ·  Admin →

  7. Run a custom SQL script when an alert is raised

    We use SQL monitor very heavily for our SQL and application monitoring, what we would like is for each alert to be able to define a custom sql script to run when the alert is raised, the output of this sql should be included in the alert.

    This would allow us to do things like capture whoisactive when blocking occurs or other application specific things and make responding to alerts MUCH easier.

    74 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…)
    7 comments  ·  Admin →

  8. Support for regular expressions

    Most of the alarms need more granular support for excluding/including different things. Using regular expression is a good idea and should be extended further. For example you defenitly need to be able to filter out things from the alarm on the sql server errorlog. Without it's useless.

    74 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…)
    3 comments  ·  Admin →
    completed  ·  Adam responded

    Thanks for this suggestion, and for the supporting comments.

    Several alerts now allow you to enter regular expressions to match text you want to ignore, to stop alerts being raised in certain situations.

    For example:
    - Deadlock (XE) alerts can be filtered by database, login name & resource (added in version 8.0.22 released November 13th 2018)
    - Blocking Process alert can be filtered to exclude queries with a SQL process names, SQL commands or objects match regular expressions
    - Job Duration Unusual alerts can exclude jobs matching regular expressions
    - Long Running Query alerts can be filtered to exclude queries with a SQL process names, SQL commands or objects match regular expressions

    We will mark this suggestion as completed, so that the votes can be returned while we continue to look at ways to make alerting more useful. Please make new suggestions for specific improvements you would like to see,…

  9. Enable and track wait stats

    I would like to see an overview of wait statistics along with historical tracking of those waits. I currently have queries that would show the total wait time, but other tools I have used will provide a current snapshot of these waits as well as store them historically so that I can monitor changes.

    72 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…)
    12 comments  ·  Admin →
    completed  ·  Priya Sinha responded

    Hi,

    We are excited to annouce that SQL Monitor v4.0 has been released. This release contains Performance diagnostics features which let you analyze the waits and queries affecting SQL Server performance on the Instance overview and Database overview pages. Check out the release notes for more details.

    Thanks,
    SQL Monitor Development Team

  10. Show the database name not just dbid in the Lock Details of a Deadlock alert

    I've got to do the extra step of:

    SELECT name,dbid
    FROM master..sysdatabases

    to figure out which database the deadlock is referring to... shouldn't have to do this.

    71 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…)
    3 comments  ·  Admin →
    completed  ·  Adam responded

    Database name is now shown for 2005+ deadlock alerts following the v4 release.

    Thanks again for the suggestion and votes.

  11. One-time Maintenance Window

    We perform updates to (nearly) all our Windows servers on our domain monthly. I'd like see the ability to set a maintenance window and have it removed once it has passed, rather than having the maintenance window fixed to set time every week.

    One use case is "silencing" alert generation while investigation is in progress

    71 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…)
    9 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

  12. Alerts related to SQL Jobs should show the job name not the job Id

    Process name: SQLAgent - TSQL JobStep (Job 0xECCD1234543A1FA439B02DE3CE12F139E : Step 1)

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

  13. Long-running query alert - add an option to exclude queries based on the USER running it

    This alert already has the options to exclude queries (via RegEx) based on the process name or SQL commands/objects used. I miss a similar option for excluding queries based on the user running the query.

    An example: let's say you have a job that runs SSIS job steps using a proxy->credential->dedicated domain user. The SSIS packages run loads of SQL queries, some taking a long time - but that might be expected and OK (let's say the job is a nightly ETL process for a DW). Without excluding queries based on that user (simple but effective!) you could get a…

    64 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…)
    9 comments  ·  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. Add an option to schedule when custom metrics run against a given database.

    Currently when a custom metric is executed can only be controlled by the frequency (daily, hourly, etc).

    My primary purpose is for daily. I would like to schedule the time of day a daily metric is run per database, or at least server. The custom metrics I pull back are time sensitive so controlling when the metric is returned is a must.

    A more advanced option to this would be going beyond simply choosing the time of day for daily runs, but rather the ability to build a custom schedule of run times. An example might be Custom Metric A…

    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…)
    12 comments  ·  Admin →
    completed  ·  Liam Prescott responded

    The ability to schedule when daily custom metrics run was added in version 13.0.56.


    To do so, when adding your metric, simply set the collection frequency to collect data every day and you can choose the time of day you'd like it to run.

  16. Show login or user in the Top 10 Queries

    Include login or user id information in the Top 10 Queries. This could help identify if a user is running an ad-hoc query.

    55 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…)
    2 comments  ·  Admin →
    completed  ·  AdminAlex (Product Manager, Red Gate Software) responded

    The Query executions feature in Redgate Monitor (available since 14.0.39 - documentation here) allows you to see the login, program, start/end times and various other information for sampled, as well as aborted or errored, queries.

    This functionality uses extended events to sample queries over a specified time threshold of 1-5 seconds.

    The Top queries functionality is driven by the dmv of aggreageted completed query information and so does not have information for specific runs, though the wait information associated with each query entry (and therefore the Top waits functionality as well) does show the login and program that experienced the wait linked to the query.

  17. Job step failure - trigger an alert, even if the job itself doesn't fail

    CONTEXT: If job step "On failure action" is set to "Go to next step" or "Go to step xy...." and the step fails, we would like to be alerted. The alert should be triggered immediately (as opposed to at the end of the job).

    PROBLEM: SQL Monitor "Job failed" alert doesn't alert in such cases.

    EXAMPLE SOLUTIONS:
    • A new alert.
    • Expanding options on the "Job failed" alert.

    53 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…)
    2 comments  ·  Admin →
    completed  ·  Carlos Eriksson responded

    As of version 13.0.55 (February 27, 2024).

    Job failing alerts can now be raised when any individual job step fails, even if the overall job succeeds.

  18. See more detail on Failed Agent Jobs

    Present the detailed Step error message for Agent Job Failures. Currently shows the Job message, but not the error from the step that actually failed. This requires the user to open SSMS and drill down to find what caused the failure, instead of getting a head start from SQL Monitor.

    53 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…)
    3 comments  ·  Admin →
    completed  ·  Adam responded

    Thanks for the suggestion and votes. This was completed in version 7.1.2. I will close this – please let us know if you believe there are further improvements we could make.

    Kind regards,
    SQL Monitor Development Team

  19. 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.

  20. exclude all of my system databases from the log backup alert

    I would like to exclude all of my system databases from the log backup overdue alert as I only perform daily full backups on them. At the moment I have to go into the Config settings and change the alert to disabled for those DBs on each servers.

    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…)
    6 comments  ·  Admin →
    completed  ·  AdminAlex (Product Manager, Red Gate Software) responded

    From Redgate Monitor version 14.15.0 we have added the ability to various database specific alert types (including the log backup overdue alert) to allow excluding databases by name via regular expression.

2 4 5 … 11 12
  • Don't see your idea?

Suggestions

Categories