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
24 results found
-
upgrade without reentering credentials
When you run an upgrade, there should be an option that just uses the current service credentials (i.e. leaves everything as is) instead of having to re-enter them.
60 votes -
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 -
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.
78 votesDaniel Rothig responded
Thanks Phil – we are considering reworking the upgrade process. If this suggestions gains more traction, we’ll prioritise it higher
-
Password is blank when accessing the edit credentials in Monitored servers
Password is blank when accessing the edit credentials in Monitored servers for the monitored sql instance .
If any options need to be changed will need to update the password for the SQL and OS credentials1 voteThe password is intentionally blank. This is to prevent users that don’t have access to the server from changing these settings.
-
Use the Base Monitor Service account to query Active Directory when using AD Credentials
We are using a Managed Service Account to run SQL Monitor so we don't have to manage passwords. However we still need to have a regular domain account to query AD because there is no option other than to specify a username and password.
What would be great is to have an option to use the base monitor service account to query AD instead of having to specify a username and password.
This would work in a similar way to what already exists when setting up credentials for the server you monitor, where you can choose to connect to the…
12 votesAD (LDAP) Auth can now be configured using the base monitor service account, this includes GMSA accounts. See https://documentation.red-gate.com/sm12/adding-sql-monitor-users/authenticating-with-active-directory
-
I would like to configure different gMSA accounts as credentials for different servers
I would like to use the more secure gMSA accounts when configuring credentials for servers that are monitored and use different gMSA accounts for different servers
1 vote -
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 votesSQL 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.
-
Detect Unsupported SQL Server Versions When Upgrading Versions
I was running v4 with a MSSQL 2005 database and decided to upgrade to v6. The installer finished successfully, however when it took me to the Web App page, there was a warning that the database upgrade did not complete successfully. The reported error was "Cannot assign a default value to a local variable". I knew right away it was a problem with my old SQL Server version. I checked the forums and indeed, 2005 is no longer supported with version 6. I understand that, and have no problem with it. However, ya'll would have saved me the headache of…
6 votes -
Use base monitor service user account to authenticate with vcenter
When monitoring a vcenter deployment, it would be nice if the base monitor service could just delegate the credentials it is running as rather than entering them in the username and password boxes inside sql monitor.
9 votes -
SQL Monitor 5.2.5 upgrade dashboard server/SQL Server memory
Upon upgrading from 5,1 to 5.2.5 the new Global Dashboard no longer shows machine memory vs. memory being consumed by SQL Server. Why was this removed? This can be critical to see if SQL Server or any other process is using up all of the servers memory.
3 votesThanks for this suggestion. Apologies for not closing this sooner as it was completed a long time ago; we did agree that we should show machine memory vs. SQL Server memory and this is shown on the Server Overview memory chart.
Thanks,
SQL Monitor Development Team -
Maintain Base Monitor Service Account between upgrades
Everytime you upgrade the base monitor (every 2 weeks), the service account that is configured to run the service gets reset to "Local System".
We have setup our system to run as a domain user to changing this everytime is painful.
The installer should respect the current user when upgrading.
3 votes -
Receive an alert for the process that is blocking not the process being blocked.
We recently upgraded our SQL Monitor to version 5.1 and it appears there has been a change in the Blocking process metric. Before the upgrade we received an alert about a process that was blocking and after the upgrade it appears we receive an alert for each of the processes being blocked. We have set the threshold for 90 seconds and if there are three processes that are 30 seconds that total the 90 seconds, we receive an alert. However we don’t want to receive an alert for the 30 second blocked processes. Is there a way we can…
10 votes -
add SSO option to the AD/LDAP logon screen
Attached file is from an application we use that allows the user to quickly logon as themselves, or to manually enter network credentials. In addition, the attached file shows a logon screen with the application version number; this too would be helpful for Redgate Monitor without having to login and check the configuration info page.
4 votes -
create user permissions script
provide the sql to run for users to use during install to assign permissions to the back end database use and the monitored db use
obviously explain about the SysAdmin problem with your product
https://forum.red-gate.com/discussion/80787/required-permissions-changed-after-upgrade
https://forum.red-gate.com/discussion/80448/new-permissions-needed-for-monitoring
https://documentation.red-gate.com/display/SM7/Permissions7 votes -
See who is using SQL monitor
Before I upgrade SQL Monitor I'd like to see who is logged in/using it so I can inform them.
2 votes -
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 votesThis was added in version 10.1.2 – you’ll see the option in the Long Running Query alert configuration screen if you update to that version or later. Thanks for the suggestion (and also to everyone who added comments)!
-
Provide a direct link to the base monitor download
When installing updates, only the SQL Monitor web service link is initially provided. In order to get access to the SQL Monitor base monitor download one has to first install the the SQL Monitor web service. This process slows down upgrade time and extends the "broken state" time in a multi-base monitor configuration.
Please provide a direct link to the base monitor download without requiring an initial WebService monitor install.
4 votes -
Report that shows top 50 long running queries across the estate
Submitting an enhancement request to expand the reporting capabilities for long running across the entire estate. The report tile only show a handful. It would be very useful to be able to run a report listing the top 25, 50, etc long running queries across the entire SQL estate. The data is available somewhere but instead of going into each instance a consolidated report would be greatly beneficial is order to identify queries for performance review. We are also going through an upgrade and are identifying queries to benchmark for before and after performance to ensure there is no degradation.
4 votes -
Exclude tempdb/ReportServerTempDB from Alerts at a GLOBAL level, WITH EASE
It makes no sense for there to be Alert configuration settings for tempdb for Consistency Checks, Backups, and any other irrelevance.
If the ONLY reason for the existence of SSRS databases is because of Microsoft's idiotic requirement for SSRS to actually be configured in 2014 before permitting an in-place upgrade to 2016, there is no ACTUAL reason why one would care two hoots about the state of either SSRS DB on ANY instance affected by this "demand". OK, I have just 21 instances to drill down to SHUT UP ABOUT SSRS DATABASES!
Please provide a better way to manage SYSTEM…
5 votes -
"Whats new" should link to the relevant release notes under "New features" tab
It currently only shows up the the release currently running, not what is in the new release. I have to search the web site to find out whether there is anything in the release that I care about enough to upgrade.
1 vote
- Don't see your idea?