Released: Dec 1, 2025

v14.4.0 での更新項目

機能

• Support for certificate authentication when monitoring Linux PostgreSQL servers is now in preview. This feature is currently only available for Windows Base Monitors running on standard Windows user accounts. Linux Base Monitors and Windows Base Monitors running on service accounts and gMSA are not currently supported.
• Added support for PostgreSQL 18.
• Custom text can now be added to alert email notifications via the alert configuration page.
• Tracking queries is now available for PostgreSQL.
• Monitoring of MySQL instances running on AWS Aurora is now supported.
• Enterprise Edition - Monitoring of Permissions is now available for Azure Managed Instances. Microsoft Entra ID is not supported for Azure Managed Instances yet.
• Virtual Machines page can now compare usage with the previous time period.
• Search and filter functionality is now available on the 'Databases in pool' table on the Elastic Pool server overview page.
• Suspended virtual machines are now sorted at the bottom of the new virtual machines table.
• Split the average / current value columns in the new Virtual Machines page in two columns (value and percentage) for better readability. The value columns are hidden by default, but can be enabled.
• When partial data has been received for the virtual machines table, we now have an indicator to show that more data is expected.
• Filtering by values is now possible in the Additional monitoring settings page.
• Replication job failure alerts and Replication maintenance job failure alerts can now be configured to ignore jobs that succeed with a failing step.
• Re-enabled and improved the performance of the Estate > SQL Server replication page.
• Added usage graphs to the details sidebar of the Virtual Machines page.
• Trials no longer begin on installation, and can instead be started from the License Allocation page at an appropriate time.
• Added 5 second and 10 second refresh intervals to the Current Activity view.

不具合の修正

• Fixed an issue where SQL Server services were not being correctly reported on configuration compliance templates.
• Fixed an issue where Get-RedgateMonitorAnnotation cmdlet didn't respect target instance.
• Fixed an issue where deleting a group then creating a new group, created the new group as a child of the deleted group.
• Fixed an issue where the last column of PostgreSQL top queries and Replica nodes was clickable despite not having a functionality when clicked.
• Fixed an issue where a selected group of a custom metric was deselected when renaming the selected group.
• Fixed an issue where alert details related to Cluster Shared Volumes were not being displayed correctly.
• Fixed an issue where toggling between template types in the Select Servers modal of Compliance Templates did not work properly.
• Fixed an issue where wait events were not shown when connected to an Oracle PDB instead of the CDB.
• Fixed an issue where the selected group is not selected after being moved.
• Fixed an issue where the selected group is not selected after being renamed.
• Fixed an issue where attempting to create a group with no name after attempting to create a group with a conflicting name displays both error messages at once.
• Fixed an issue where creating a new group with no name after cancelling a new group with an acceptable name creates a new group with the cancelled name.
• Fixed an issue where an option to expand a query wouldn't appear.
• Fixed a performance degradation of TopQueries.
• Fixed an issue where memory usage gradually increased in Base Monitor when repeatedly attempting to connect to an unreachable server.
• Reduced number of locks introduced by SQL Server backup sampler (Can be disabled by switching off the feature flag 'UseNoLockSqlServerBackupSampler').
• PostgreSQL SSL authentication errors should now be correctly categorised by Monitor.
• Pinning an entity on the global dashboard should no longer cause other entities with the same name to also be pinned.
• Clarify the Database cluster identifier needs to be specified when adding or editing the Host monitoring credentials for PostgreSQL instances on Aurora clusters.
• Azure Managed Instances should no longer appear as being in an error state if non-fatal database connection errors occur during sampling.