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.


240 results found

  1. Traceflag 1222 for deadlocks

    Use traceflag 1222 for deadlocks when monitoring SQL 2005+, and keep 1204 just for SQL 2000 instances. 1222 gives so much more information and doesn't cut off the SQL text.

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hello,

    We are pleased to annouce that this feature is now implemented as part of v4.0 release. Please check release notes for more details.

    Thanks,
    Priya

  2. Add an option to alias the server names.

    In a multi-server environment it would be very helpful to be able to assign an alias to the server name. So at a glance you can see something like - 192.168.1.1 (Company A OLTP)

    Merged idea: Longer descriptions for Servers, Databases etc

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Closing this suggestion as the server alias work was completed in v5.2.2.

    However, there is not currently a way to alias cluster/machine names, so if that is important please raise it as a new suggestion as we could look to address it if there is demand.

    If you are experiencing problems with server aliases, please let us know via the support forums.

    Thanks

  3. Use (Group) Managed Service Account Credentials for Server Monitoring

    Allow the use of managed service accounts (MSA and gMSA) as credentials when monitoring servers.

    Given the high-level permissions required to fully monitor servers, this would provide a higher level of security to match.

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  7 comments  ·  Admin →
  4. SQL instances which are part of Availability Group does show if it primary or secondary in Global Dashboard

    When SQL instances which are in Availability Groups are being monitored, the global dashboard lists both the primary & secondary node.
    However though it does have 'AG' badge but it does not say which is primary or secondary.
    While looking at the SQL monitor it will key that we know upfront which is the primary instance and also when alerting it should say primary or secondary in the subject line.

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Admin →
  5. Exclude specific alerts from SQL SERVER ERROR LOG ENTRY alerts

    We have certain tools (mainly infosec related) that generate a lot of entries in the SQL server error log as part of their normal operation creating a lot of alerts. The only way to identify these and thereby determine that they are 'expected' is to go into each alert individually and mark it as read. The ability to ignore certain errors based on error number, severity or message would add a lot of value to this feature.

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  7 comments  ·  Admin →
  6. TempDB unexpected growth

    I think it would be a good idea to have information about what caused random sudden growth in tempdb. I know we can see the DB size chart but theres no way to know what caused it.

    Information that would be nice to be captured:

    Table name
    What query created table
    What user created table

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    TempDB metrics are now available on the server overview page from version 11.0.

  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)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  8. Show a log of query activity

    CONTEXT: When investigating a performance issue, I want to know what has been running

    PROBLEM: SQL Monitor has rich query information on the overview screens, the performance diagnostics panels, and the query alerts, and the query trace in alert detail reports, but it's difficult to tie that information together

    EXAMPLE SOLUTIONS:
    - Implement a query log
    - Show query information on the analysis graph

    45 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 →

    The Query executions feature in Redgate Monitor (available since 14.0.39 - documentation here) allows you to see the login, program associated with the query as well as the start/end times and CPU time, as well as 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.

  9. deadlock

    Add the ability to customize deadlock alerts. I want to able to ignore alerts if the deadlock was on table XXXXX or produced by stored procedure YYYYYY
    or have different alert levels depending on the database and table.

    45 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Thanks for this suggestion. We will close this now as there have been no new comments since we released the new filters.

    However, please do raise new suggestions for anything you feel hasn’t been addressed, so we are able to consider them as we continue to improve SQL Monitor.

    Thanks,
    SQL Monitor Development Team

  10. add the ability to have multiple users

    It would be benefical to have an admin account that can allow config changes to be made and also a "guest" user which could review the data that was collected but not modifiy the settings.

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  11 comments  ·  Admin →
  11. Have ability to sort list of databases on SQL Instance overview

    It might be helpful to have the ability to sort these by name, esp. when this list happens to be quite long. It seems like under the current design they are sorted by database ID.

    I have to scroll past 50+ db's to see the remaining info on the UI - can this be improved? Collapsing the list or adding some filtering, e.g. filter to limit to x# which is then changeable by page index, or filter by other than OK status

    43 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

    This list is sortable as of SQL Monitor 4.0 (it is also truncated by default, making it easier to scroll past it)

  12. Include Stored Procedure performance

    Include which stored procedures executed have high CPU, memory utilization, IO consumption. Also, include top wait types on Global Overview in addition to CPU and Memory

    43 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

    The most performance-relevant stored procedures and ad-hoc queries can be inspected with the “Performance Diagnostics” feature on the Instance and Database Overview screens. This information is also replicated in the Performance section of the alert details pages

  13. Alert when SQL Monitor is having a problem.

    We have the SQL Monitor database located on a different server from the Base and Web Service. We had an instance where the SQL Server hosting the SQL Monitor database went down. When that server went down it failed to send us an alerts and we didn't know that SQL Monitor was having no problems as it wasn't sending out any email alerts to notify us that it couldn't connect to it's database. A nice fix would be to have SQL Monitor send an alert to notify us that it can't do it's job.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    This can be set-up using the 'Send base monitor error emails to' field within the Email notification settings (see attached). SQL Monitor will send error emails to this email address if a base monitor experiences an error.


  14. Block Specific Deadlocks by Lock Details

    We've just updated to SQL Monitor 6. We was hoping there was a feature in this to change alert settings for Deadlocks with specific lock details rather than just all Deadklocks.

    For example
    we don't want email alerts on: Deadlock 'object: ReportServerTempDB.dbo.SessionLock, lock mode: Exclusive (X), index: IDX_SessionLock

    However we wish to receive emails when: Deadlock 'dbid: 6, object id: 72057594038845440, index id: (9bf78693a4b4)'

    However this feature doesn't exist. Would be great to have added to an update in the near future!

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Thanks for this suggestion and the comments.

    As previously announced, since version 8.0.22 (released November 13th, 2018) Deadlock (XE) alerts can now be filtered by database, login name & resource, and victimless (eg Exchange Event) deadlocks are excluded by default.

    We are marking this as complete, but please do let us know if you have any further feedback.

    Thanks,
    SQL Monitor Development Team

  15. Select multiple counters for Analysis

    It would be helpful to see and compare multiple counters for an object in the Analysis tab.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    SQL Monitor v 3.3 has been released. This release contains ability to display multiple metrics in the same Analysis graph to identify correlations and unusual patterns of behavior more easily.

    Thanks
    SQL Monitor Development Team

  16. Add previous/next navigation to Alert Details

    On the Alert Details screen it would be extremely convenient to have the ability to navigate between issues within the same screen. Right now you have to either go back through all of the screens to get back to where you initially went to view the details of the alert, or use your browser's back button, which gives inconsistent behavior. This makes going through a high volume of alerts tedious and cumbersome.

    This could be handled by something as simple as a "previous/next" buttons on the Alert Details screen. Something akin to the "oldest/older/newer/newest" buttons on the Alert Inbox screen.

    …

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We have now implemented this suggestion in v3.1.

    During our usability testing we found that ‘newer/older’ was less ambiguous than ‘previous/next’. Filters now persist on the Alert inbox until they are manually cleared, so you can navigate away and always return to the filtered alerts.

    We’re interested to hear your feedback on this feature so please let us know at usability@red-gate.com. Thanks again for the suggestion and comments.

  17. Add mirroring monitoring

    I may be wrong but I can't see that you have the capability for mirroring monitoring in the tool. This would make a more persuasive case for replacing Idera if this tool was included.

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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)
    You have left! (?) (thinking…)
    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

  19. Sort or Filter Monitored Servers

    In Configuration -> Monitored servers I would like to sort and filter the servers and have the grouping functionality applied to this screen. This would make it easier to find my server that I want to put a maintenance window on.

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. It would be grand if I could change the time format.. 12 hour clocks just don't sit right with me.

    It would be grand if I could change the time format.. 12 hour clocks just don't sit right with me.

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We have just released version 6.0.7 and this update means the clock can now be displayed in either 12 or 24 hour format – this can be toggled at Configuration > Display settings.

    Thanks for your patience.

    SQL Monitor Development Team

  • Don't see your idea?

Suggestions

Categories