Released: Mar 11, 2026

v14.11.0 での更新項目

機能

• Index sampling is now enabled by default for all PostgreSQL instances. This will result in a change of configuration if it was previously disabled. It can be disabled by visiting the "Additional monitoring settings" section of the "Configuration" page.
• Added Machine: processor time (excluding steal) metric for Linux hosts on the server overview, showing CPU usage excluding hypervisor steal time.
• Added support for AI analysis of Top queries for MongoDb instances.
• The Get-RedgateMonitorServicePrincipalCredential, Add-RedgateMonitorServicePrincipalCredential, and Remove-RedgateMonitorServicePrincipalCredential cmdlets now support AWS credentials using the -Provider AWS flag, in addition to Azure credentials.
• Modernized the Configuration information page with collapsible base monitor details to better support larger estates.
• The blocking processes table now shows system processes and the blocking process alert now alerts about system processes.
• Improved performance when loading host-level metrics (CPU, disk I/O, memory), when running the Base Monitor with TimescaleDB repository.
• Enterprise edition - SQL Audit now supports all action types that belong to the DATABASE_PRINCIPAL_CHANGE_GROUP.
• Added AWS EC2 cloud details support in the Estate > Virtual Machines page (and the ability to add credentials) for Monitor SaaS.
• Changed the default working directory for PowerShell script alert notification from the Base Monitor installation directory to %TEMP%, existing scripts that rely on the previous working directory will need to be updated to use absolute paths or change their working directory within the script.

不具合の修正

• Fixed an issue where filtering a database in the custom metric test UI would have no effect when performing the test.
• Fixed an issue where SQL Backup compressed backups could be stored with incorrect size, compression, and encryption data if Monitor sampled during SQL Backup's post-processing window.
• ServiceNow URLs are no longer required to follow a specific format in notification settings.
• Fixed an issue in Estate > SQL Server versions for customers who have disabled automatic refresh of the latest available updates of SQL Server. A notification about the freshness of update data was incorrectly based on a stale update file, if still present.
• Fixed an issue where the script notifications set the $AlertData.Target.MachineName to the cluster name and set the $AlertData.Target.ClusterName to null.
• Fixed an issue where the script notifications set the $AlertData.Target.FailoverClusterActiveNodeName to null for certain alert types.
• Fixed an issue where Analyze query functionality in Server overview > Current activity tab was not working in some cases on IIS hosts.
• Fixed an issue where custom metrics imported from the external library could not be installed on a specific base monitor when multiple base monitors were configured.
• Fixed an issue where servers could show as Green/Healthy on the overview page when they had alerts suppressed.
• PostgreSQL connection strings will no longer enforce the 'C' locale for time and date formatting.
• Filtering on the alerts page now works properly when there are multiple Base Monitors that each have custom alerts.
• Fixed an issue where Redgate Monitor did not correctly detect some types of connection error for an Azure Database for MySQL Flexible Server.
• Enterprise edition - Fixed a loading error on Security > Users Tab when clicking on a user to view details.
• Fixed an issue preventing stored procedure statistics from appearing in the Top Procedures tab for Azure SQL Database.
• Fixed an issue where the PostgreSQL index usage chart could appear empty for users outside the UTC timezone.
• Reduced the frequency of Windows authentication attempts when monitoring a SQL Server instance with invalid credentials.
• Fixed an issue where a Backup Overdue alert could fire incorrectly when the most recent backup was copy-only, even if a valid regular backup was within the threshold.
• Fixed an issue where PostgreSQL top queries collection would fail after upgrading the PostgreSQL server without updating the pg_stat_statements extension.