Postgres Enterprise Manager 10.1.0 release notes v10

Released: 15th May 2025

New features, enhancements, bug fixes, and other changes in Postgres Enterprise Manager 10.1 include the following:

Highlights

  • Support for monitoring and switchover of Patroni clusters
  • Automatic tagging of node roles in PGD clusters
  • Improved support for HA PEM architectures
  • Resolved the issues with Kerberos authentication on RHEL 9

Enhancements

DescriptionAddresses
Added support for monitoring and switchover of Patroni clusters.

PEM 10.1 includes a new 'Patroni Cluster Status' to collect information from Patroni. This information is displayed in the Streaming Replication dashboard for Patroni nodes. Additionally, PEM now includes five server-level alert templates for Patroni nodes:

  • Patroni cluster paused
  • Patroni DCS not healthy
  • Patroni down or out of contact
  • Patroni no leader detected
  • Patroni timeline mismatch
PEM now automatically tags PGD nodes with their role.

A new probe 'PGD Node Roles' has been added to PEM. This probe collects the roles of each PGD node. The data collected by the probe is used to automatically label nodes by role.

Added support for multi-host connection strings from web application to PEM server

When configuring a PEM web application, you may now provide multiple host addresses for the PEM backend. The web application will try each in turn until it finds one that accepts write connections. This should be used in conjunction with a suitable High Availability architecture.

Added support for multi-host connection strings PEM Agent to PEM backend database server.

When configuring a PEM agent, you may now provide multiple host addresses for the PEM backend. The agent will try each in turn until it finds one that accepts write connections. This should be used in conjunction with a suitable High Availability architecture.

Introduced a pem.register_pem_server(server_id) function to allow registering a database server as a replica PEM server

When configuring a High Availbility PEM architecture, this option may be used to register additional copies of the PEM backend. The function creates static system tasks for all these servers, but they are disabled by default. They will be enabled only for the primary. After promotion, the new primary PEM server will take over the system tasks automatically. This removes the dependency of server/agent id 1 to run the system jobs which existed in prior versions of PEM.

Added new API version v14
Introduced a Steps sub-panel within the Scheduled Task detail view.

This panel displays all steps associated with a task, along with the last run status and execution time of each step, enabling better visibility and monitoring.

Added `--cluster-name` switch for pemworker to specify cluster name when registering agent/server.
PEM Agents can now be included in Clusters
PEM can now call a webhook on job completion/failure.

When configuring a webhook endpoint. You may now choose between 'Alert' and 'Job' webhook types. Webhooks of type 'job' will be fired according to the notification settings of each job.

Added the ability to enable disabled probes from charts that depend on them.

Changes

DescriptionAddresses
Merged pgAdmin4 9.2.

PEM 10.1 is based on pgAdmin 9.2 and therefore inherits the majority of fixes and features from this release.

Added ability for PEM to display info messages on charts, for example if data is missing.
Added pywinpty package to dependencies on Windows.
Jobs which are created by an alert are no longer listed in the PEM object explorer.

Jobs created by alerts were previously visible in object explorer. This led to confusion as users were able to edit these jobs in unintended ways which would typically result in breakage.

Bug Fixes

DescriptionAddresses
Fixed an issue whereby an error in a dashboard would prevent all subsequently accessed dashboards from loading correctly.
Fixed an issue whereby psycopg errors would occur while authenticating PEM using kerberos on RHEL 9

PEM is now fully compatible with Kerberos on RHEL 9, so users of this combination are recommended to upgrade to PEM 10.1.

Fixed an issue whereby dashboards were not updated after being edited.
Fixed an issue whereby custom probes with special characters in the probe code were not created properly.47765
Fixed an issue in SQL Profiler whereby 'stop trace' was not working as expected.
Fixed an issue where probe configurations were not getting saved from UI upon changing the values.
Fixed an issue whereby EFM probes would fail due to a JSON data parser exception.46527
Fixed an issue where date in Alert Status table yields year as 1970.
Fixed an issue with the streaming replication chart where the user would see an error `Column "Cluster Name" does not exist`.47332
Fixed an issue which could result in an error `The error - module 'lib' has no attribute 'X509_V_FLAG_NOTIFY_POLICY'` during PEM configuration.
Fixed an issue whereby a "threshold" key error was occurring on update of Alert fields other than threshold values.
Fixed an issue whereby charts were not automatically refreshed after being modified.
Fixed an issue where the chart legend was not being accessible.
Fixed an issue whereby Audit Manager would not display a useful message if no EPAS instances were found.
Fixed an error that could occur in the browser when performing EFM switchover from PEM.
Fixed an issue where the Alert Templates page didn't display properly after adding a new template.
Fixed an issue where Alerts were disappearing from the Manage Alerts panel after selection of objects in cluster type node.48476
Fixed an issue where special characters in column names caused unexpected behavior in Capacity Manager charts.
Fixed an issue where the tooltip doesn't go away after moving the pointer off a chart.
Error catching logic missing in render_as_query function of linechart.
Improved exception handling when running `agent_ssl_passphrase_script` script.
Fix for NaN values in PieChart.
Fixed an issue in Email Groups whereby the delete button would be enabled on the default group when it should be disabled.
Fixed bug that would cause 'duplicate key' errors in browser console logs.
Fixed an issue with the webhook 'test' button state whilst waiting for a response.
Fixed a PEM configuration failure on NGINX/uWSGI when UMASK is 0027
Fixed an issue whereby NGINX could not be started when ipv6 was disabled
Fixed an issue whereby Alerts were not saved when execute_alert_on was toggled.
Fixed an issue with redirects after editing a dashboard.
Fixed an issue where breadcrumb tree was not displaying properly when a dashboard was opened from the context menu.
Fixed the missing teams field from the Register/Edit server dialogue. Also added the privilege check while registering the server.