Redgate Monitor v14.2.0

Released: Oct 29, 2025

v14.2.0 での更新項目

機能

  • Custom metrics and alerts are now available for PostgreSQL.
  • Added new alert types for Replication job failure and Replication maintenance job failure for SQL Server instances. These new alert types replace the existing Job failure alert type for replication jobs.
  • Added Estate > SQL Server replication page to display the latest activity of replication jobs.
  • Added Estate > Virtual machines page to monitor virtual machine usage.
  • Added a feature flag (OnlySampleEnabledActiveDirectoryUsers) that can be switched on to stop Monitor from sampling Active Directory users whose accounts are disabled.
  • Updated the Analysis page with a new modern design.
  • Alert configuration save failures are now displayed in the UI with clear error notifications.
  • The export 'All data' button on the Security page grids will now also export hidden columns.
  • The job failure alert and the job canceled alert now displays the job category in the alert details.

不具合の修正

  • Fixed an issue causing intermittent failures in sending notifications for alert closure events, introduced by a regression in version 14.1.0.
  • Fixed an issue where opening a new tab on the current activity filters were not persisting after closing and reopening the tab.
  • Fixed an issue when adding an Oracle instance on an Amazon RDS environment, the service name label mentions pointing to the "container database" rather than the "PDB".
  • Fixed an issue for TimescaleDB repositories that could result in custom alerts being shown with an incorrect name for a monitored server.
  • Fixed an issue where renaming a parent group loses the child group level alert configuration.
  • Fixed an issue where moving a child group to a different parent group loses the child group level alert configuration.
  • Fixed an issue where deleting a parent group whose child group had alert configurations retained the alert configurations (upon restoring the parent group and child group).
  • Fixed an issue preventing custom alert settings from being configured properly for certain monitored servers.
  • Fixed an issue where failing SQL server replication jobs raised Job failure alerts that could not transition from Active to Ended.
  • Fixed an issue where the blocking process alert incorrectly included unrelated child processes and reported inaccurate blocking durations.
  • Resolved an issue where retrying individual query monitoring on a non-existent file resulted in a connectivity error.
  • Scheduled reports will no longer fail to send if website is bound to all IP addresses (0.0.0.0 or [::]).
  • Switching the inheritance level of a custom alert should no longer cause the page to fail to load.
  • Editing a custom metric with Azure Managed Instance or Azure SQL DB as one of the targets should now populate all the metric fields as expected.
  • Deeply nested Postgres query plans no longer disrupt monitoring.
  • The Job failure alert type (default severity: medium) no longer applies to SQL Server replication jobs. Replication jobs are now covered by the new Replication job failure alert type (default severity: high), or Replication maintenance job failure alert type (default severity: low). The job failure alert type continues to apply to non-replication jobs.