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.


  • or

733 results found

  1. Backup overdue alert - RegEx filter

    I have many non-production databases on production SQL Instance, that make no sense to backup. I know I can turn this alert off one by one on each database. RegEx filter by database name would be help.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We would like to send slack messages to different channels depending on the server.

    We have multiple teams who are ultimately interested in what is wrong with their platform, The posting to a single slack channel is good, however giving an option to send only messages from certain servers to specific channels would improve our customer engagement. currently the main channel is ignored by the all teams except the dba's as the chaff from other servers can cause disinterest, or interest when no reason for a team to investigate.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Suspend Monitoring of Individual Cluster Nodes

    Alert suppression windows can be applied to groups, clusters, instances, and machines - including individual cluster nodes. Howerer it seems it is only possible to suspend monitoring for instnaces or clusters not individual nodes,

    We recently had a hardware fault and it would have been helpful to suspned monitoring of a specific node whislt the engineer resolved the fault.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. "Installed Versions" tab needs to be aware of GDR updates

    Only Service Packs and Cumulative Updates are currently included in the version list maintained by Redgate, which drives the "Installed Versions" tab. GDR updates are not included.

    In my estate, this has resulted in SQL Server 2012 SP4 installations showing as being fully up to date, when there is a GDR update from January available, to address Meltdown/Spectre.

    Microsoft's official line on GDR updates for SQL Server is:

    "A GDR addresses an issue that has a broad customer impact, that has security implications, or that has both. A GDR is determined and issued by Microsoft as appropriate and when appropriate.…

    6 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 →
  5. Show current data sizes on purging page

    On the data purging page would it be possible to show for each of the data categories how much space each one is currently occupying.

    Possibly even an 'oldest date' too? As this may be pertinent if the purge thresholds haven't yet been met.

    On some environments I want to keep as much SQL Monitor data as possible and if it's a healthy server you may have very little alert data, and so want to keep more history than you do say, machine data.

    It would also help in cases where the Repository database is growing, and you're not sure…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add scheduling for monitoring suspension and resumption

    Using Azure SQL Database in serverless mode with an auto-pause is a useful feature to save money when the db is not in use. SQL Monitor keeps the db from sleeping overnight.

    Suggest addition of scheduling for Suspend/Resume operations, similar to alert suppression scheduling.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Apply filters to more SQL Server alerts

    In configuring Long Running Query, I'm able to specify a filter on the process name (e.g. wanted to exclude my "Barracuda" backup processes - and did so successfully). I'd like to do the same for other Alerts such as Deadlocks and Blocking Processes.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. use alternate IP addresses for named instances

    I am modifying my named instances to use separate IP addresses. This allows me to use CNAMES for each databases, We are then able to move the databases around to another instance without the customers having to modify their connection strings.We are also able to use port 1433 for all existences. SQL monitor tries to connect to the instance using the servername\SQLINSTANCE, which no longer works remotely suite to each instance having it's own IP Address using and alternate A-RECORD name.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  9. With the AG Groups it would be good to have soft alerting on configurations

    With the AG it is possible to have different configuration on the server replicas. We mostly get caught out with Logins. but have had issues with XMLBlob size, linked servers and Server Master Keys.

    It would be good for monitor to alert (or be able to alert) if a Login does not exist on both (all) replicas. we have times when a quick addition through SSMS does not put the same login on all side. when fail over occurs we then have broken processing. It would be good for sids to be checked as well as this is another…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. network adapter name on overview page

    Currently network adapters' interface description is shown on the overview page of a monitored server. i am not interested of that information really, I would see the net adapter name as Get-NetAdapter cmdlet returns. So, Name should be there instead of the description.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Simpler Upgrade \ Patch Process

    The upgrade process is a bit long winded. It would be great if the system could be upgraded or patch with a single click. Ideally within SQL Monitor but if not, downloading the file and just selecting upgrade would be great.

    83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Daniel Rothig responded

    Thanks Phil – we are considering reworking the upgrade process. If this suggestions gains more traction, we’ll prioritise it higher

  12. MONITORING ERROR (SQL SERVER DATA COLLECTION) more infromation

    Is it possible to list the items that failed in the alert?

    In the description for this alert it notes that one or more of the following connection methods failed:
    WMI
    Remote registry (PerfMon and registry access)
    Remote file access is not set up (hidden administrative shares should be enabled)
    SQL connectivity

    Is it possible to note in the alert details which one failed? It would make troubleshooting after the fact a bit easier.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  13. Identifiy the failed job steps when a job has failed

    CONTEXT: When looking at a job failed alert, we would like to pinpoint why it has failed.

    PROBLEM: SQL Monitor doesn't indentify the failed steps - we have to go to SSIS to get that information.

    EXAMPLE SOLUTIONS:
    • Add this information to the "Job failed" alert
    • Provide a query to make retrieving this data more convenient

    136 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. Failed job steps are now listed in failed job alerts – this feature was completed in Version 7.1.6, released October 4th 2017 (apologies for not updating sooner).

    We have marked this as completed – please let us know if you believe this needs to be reopened, or add a new suggestion if you would like to see a particular improvement.

    Thanks,
    SQL Monitor Development Team

  14. Cluster Roles that have been renamed should no longer have an entry with the old name

    Over the last year and a half I have migrated several SQL FCI's to new windows clusters, new hardware, windows and SQL versions. To accomplish this with minimal downtime I had to setup the cluster roles ahead of time with everything ready to go prior to doing a final tlog backup/restore and rename of the cluster instances. This has worked well for us however SQL Monitor creates a new server record when the instance is renamed and never gets rid of the original name of the the new instance. This has left me with SQL Monitor still showing this nonexistent…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  15. Alerts should configurable to repeat until an issue is resolved

    We'd like the option for alerts to repeat until an issue is resolved. For instance, we may have a custom alert to tell us when a DBCC CheckDB hasn't been performed in >24hrs. For that we'd perform the check once per day and expect to get an alert every day that the problem continues. Without the alert recurring it's very easy for it to slip through the cracks and get missed.

    Another example is blocking. We have some databases where we monitor blocking via SQL Agent and when a block occurrs for 1m or more, we send emails every 30s…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Disk Names in Overviews and Analysis

    Disk Names in Overviews and Analysis

    Hello,
    I think that it will be usefull to have a same disk names in Overviews and Analysis as they are shown in the system in Disk Management.

    ServerData (F:)
    Server
    Logs (G:)
    Server_System (H:)

    Not only F: G: H: as they are visible now in SQL Monitor.
    Thank you.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  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. Deal better with extremely spikey data

    CONTEXT: Some counters displayed by SQL Monitor is extremely spiky. SQL Monitor scales its graph such that the any spike fits on the y axis

    PROBLEM: If there is one extreme spike, all the other data gets scaled such that it's very close to the x-axis, making any patterns in the data hard to see.

    EXAMPLE SOLUTIONS:
    • allow to manually zoom into the y axis
    • allow extreme spikes to be beyod the drawing area of the graph (still with some indicator of how high the spike is)
    • have an option to show the graph on a logarhithmic…

    136 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Remove node from sql monitor for sql clusters

    If i have a SQL cluster that has a non SQL witness I would like to just remove it so it does not get pulled into the warning system or the dashboard.. i in my case am using a NAS machine as a witness to the cluster.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  20. Add alias with powershell module

    We install our sql server automatically via powershell, so we also add them there to the monitoring. We would like to safe us work, by giving the server a custom alias while adding to the monitoring as it can be done through the website.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  • Don't see your idea?

Suggestions

Categories