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.

219 results found

  1. Monitor SQL Server 2014 failover clusters with Cluster Shared Volumes

    There is currently some trouble with monitoring a windows failover cluster with CSV - specifically, the error log is unreachable because base monitor apparently connects to the wrong network name to access files.

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

    As mentioned in the comments, this was completed in v5.2.7
    (relevant issue was SRP-10451: Cannot retrieve log files for users who monitor SQL Server installed on a clustered shared volume).

    Apologies for not updating this at the time.

    Thanks
    SQL Monitor Development Team

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

  3. See how alerts correlate in time

    CONTEXT: When investigating an alert, it is useful to see what else has happened at the time. SQL Monitor gives detailed performance and query data with every alert details report, but doesn't show what other alerts have been raised at the time

    PROBLEM: Sometimes alerts inform one another. E.g. a Long-running query can be caused by a blocked process, or a deadlock can cause a job failure. Alerts coinciding with the current one potentially help us to determine the root cause

    EXAMPLE SOLUTIONS:
    • List time-correlated alerts when viewing alert details
    • See alerts over time on a graph
    •…

    38 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  ·  Adam responded

    Version 6.0 was released on August 30th, 2016 and contained a new Server Overview which shows alerts over time.

    I am closing this as there have been no new comments since it was released. If you would like to see specific improvements to this feature, please raise a new suggestion.

    Thanks,
    SQL Monitor Development Team

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

  5. Triage and configure repeating alerts more efficiently

    CONTEXT: Some alert types such as Long-running queries, Job Failure or Error Log Entries can trigger very frequently under certain circumstances.

    PROBLEM: This causes a large number of alert emails to be sent, and the only way to ascetain that all these alerts are the same is to view the details screen for all of them.

    EXAMPLE SOLUTIONS
    • Group similar alerts in the alert inbox
    • Raise alerts not on individual events, but on these events happening a specified number of times
    • Mention identifying information sooner: e.g. directly in the alert inbox
    • Suppress query-based alerts for specific…

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

  6. Make SQL Monitor scale to more machines and networks

    CONTEXT: We want to monitor many different servers in different domains and locations

    PROBLEM: Network configuration for cross-domain monitoring can be challenging, and SQL Monior can slow down if many servers are being mointored

    EXAMPLE SOLUTIONS:
    • Create a central web interface that can access multiple Base monitors
    • Provide an optional agent that can be deployed for easier network configuration
    • Make a single installation of SQL Monitor scale to a larger number of servers, and make network configuration easier

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

  7. Forecast and plan disk/database capacity

    CONTEXT: When looking after a large number of databases, we have to make sure that none of them run out of space or I/O capacity.

    PROBLEM: SQL Monitor needs to show us:
    • The current size of Database files (and which disks they are on) and how full they are, ideally with a forecast
    • Autogrowth configuration
    • Space remaining on disk, ideally with a forecast
    • File and disk-level IO metrics, ideally with a forecast

    EXAMPLE SOLUTIONS:
    • Provide this data as metrics in the Analysis Graph
    • Create a Disk Overview report with this data
    • Enhance the…

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

    Thank you for this suggestion. Version 8.0.10 released July 10th, 2018 includes a new Estate tab containing the new “Disk Capacity Planning” feature.

    We hope this meets the requirements and will close this suggestion, but please do raise another suggestion if you have specific improvements you’d like to see.

    Kind regards,
    Adam
    SQL Monitor Development Team

  8. Suppress performance-related alerts during maintenance periods

    CONTEXT: I expect my system to slow down during routine maintenance tasks, which often leads to false postitives for performance-related alerts (long-running queries, High CPU...) in SQL Monitor.

    PROBLEM: While I could configure a maintenance window where alerts don't get raised, this would also suppress operational alerts (e.g. Machine unreachable, Job failed) - these are still relevant while maintenance is in progress

    EXAMPLE SOLUTIONS:
    • Allow to configure maintenance times for individual alerts
    • Change maintenance window behaviour so that operational alerts are still active during maintenance

    What do you think about these solutions? Got another idea? Let us know…

    233 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…)
    24 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

  9. Only receive emails for the most important alerts

    CONTEXT: I review alerts raised by SQL Monitor in order to stay on top of my server activity, and I also have alert emails enabled in order to respond quickly to issues.

    PROBLEM: I only want to receive emails for issues that require immedate action or are otherwise noteworthy. I don't want to change the alert thresholds because for my triage, the "lower-priority" alerts are still interesting - but they shouldn't be sent as emails.

    EXAMPLE SOLUTIONS:
    • Send emails by alert priority - e.g. medium and high only
    • Alter the default alert behaviour to only send emails for…

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

    We have released version 9.0.10 of SQL Monitor which includes the ability to choose to receive notifications for only high level alerts, or only high and medium alerts (or the default of all severities) globally.
    https://documentation.red-gate.com/sm9/release-notes-and-other-versions/sql-monitor-9-0-release-notes

    We realise this is long overdue, as we’ve struggled to provide one solution to the different problems contained in this suggestion. As such, we’ve decided to break this down into different problems we can look to address.

    We believe this release delivers the solution to the problem originally suggested, to be able to send email notifications for alerts with a Medium or High priority, so will mark this as completed. However, please do raise new suggestions for anything you feel hasn’t been addressed by this release, so we are able to consider each one as we continue to improve SQL Monitor.

    Thank you for your patience,
    SQL Monitor Development Team

  10. Single sign on

    Make it so that I can add an AD group to the settings, then enable AD Auth in IIS and not be prompted for username and password.
    LDAP settings should not be needed.

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

    Support (at) red-gate.com can provide you with instructions how to disable SQL Monitor authentication in order to fall back on IIS authentication, which supports Single Sign On.

  11. Raise Alert level based on time

    Currently all alert levels are based on the numbers allocated and the alert is simply triggered at that level,

    Some of the values I'm tracking sit at 0 quite often, the problem is less the number but the length of time that it remains at that number

    So after 5 collections i would like to raise a low alert, after 10 collections a medium and after 20 a high alert

    Thanks for your time and concideration

    Ste

    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 →

  12. A report on the front page (Overviews) of the Sql service status

    A report on the front page (Overviews) of the Sql service status (Datbase Engine,Agnet,Reporting Service And etc )

    Using DMV "SYS.DMSERVERSERVICES"

    This Report includes Columns For Example : ServiceName,Startup-Type ,Status-Desc And Last Startup Time

    Tnx From Redgate Company Team

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

    Unhealthy service statuses raise alerts in SQL Monitor, which will be surfaced on the front page (future work on the front page will make this more parseable in SQL Monitor 5.2)

  13. A version support page

    Add a page on your site to list the current versions (liked to release notes) and all previous versions so we can easily see how many versions back we are or if we are at the latest one.

    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 →

  14. Description of Full scans/sec

    In Explanation it says
    "a lot of index scans may indicate missing indexes"

    I guess it should be "full scans" ?

    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 →

  15. Check both full and differential backups for the overdue alert

    As it is, the backup overdue alert will not check if a differential backup has been run.

    Example: We have a database with simple recovery model that is set up to make a FULL backup every week, and a differential backup every day. If the alert level is set to "more than one day" then it will be triggered even though the diff backup has been run, indicating that it is not overdue.

    We could set (and do that) the alert level to check only for "more than 7 days", but then we will not be notified if a diff…

    26 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  ·  Adam responded

    Thank you for this suggestion, and apologies for not updating sooner.

    We believe this was solved when the Differential Backup Overdue alert was added in Version 8.0.7 (May 2018) . This alert is raised when entries for a differential or full backup in the [msdb].[dbo].[backupset] system table are older than the time you specify.

    We will mark this as completed but please do let us know if you have any further feedback.

    Thanks,
    The SQL Monitor Development Team

  16. Summary alert page ordered by active alert type with drill down to detail

    In the previous red gate alert program it had a summary by each alert giving a quantity for the selected monitor period and one could then drill down to the detail for that specific alert in chronological order starting with the most recent - found this most useful - also gave a simple measure of occurrences over time which one could use to track the effectiveness of efficiency projects

    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  ·  Adam responded

    Thanks for the suggestion – we believe this has been addressed with the Grouped Alerts released in Version 7.1.18.

    We will close this suggestion, but please do raise another suggestion if you have other specific improvements you’d like to see.

    Kind regards,
    Adam
    SQL Monitor Development Team

  17. increase or decrease the fill factor

    Dear team.

    I see some explanation on the sql Monitor live Demo tool which seems incorrect:

    Check also: The fill factor percentage of the tables in your indexes. If enough space for index expansion is available on data pages, the potential for page splits is reduced. The default fill factor value setting is 0 (100%), which means that pages are filled to capacity. If you increase the fill factor, additional free space is left in the indexes after they are rebuilt or reorganized, helping to prevent excessive page splitting

    increase should be decrease: the higher the fill factor the less…

    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 →

  18. Overlap

    To analyse a trend over a period of say 30 days using one continuous line graph is difficult. If we could see a line for day 1, overlapped with day2, day 3 etc over the same 24 hour period then its easier to see trends and patterns e.g. processing time increases at 1pm everyday

    Regards

    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…)
    1 comment  ·  Admin →

  19. Sort filter for manage server screen.

    We have many development and test servers we want in our server list but not fully monitored. They were added to Monitoring after the production boxes, so they are on top of the list.

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

    You can use Groups to create filtered views of the Global Overview screen – improvements to that screen will mean that you won’t need to use the Manage Servers screen to inspect your system in the future.

  20. Allow filtering out certain types of wait statistics (e.g. to remove benign ones)

    As the title says. See Paul Randal's query for an example: https://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/
    Give us the option to control exactly which types are filtered out of results.

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

    These are specified in the SQL Monitor database, as an entry in [settings].[KeyValuePairs]

1 2 … 5 7 9 10 11
  • Don't see your idea?

Suggestions

Categories

Feedback and Knowledge Base

(thinking…)