Chapter 10. What’s New in PPEM 2.9

Release date: 2026-08-27

For upgrade instructions, refer to Chapter 73.

PPEM 2.9 introduces the following major upgrades and improvements:

  • Expanded the control center capabilities by adding the ability to view clusters alongside instances.

    For more information, refer to Chapter 50.

  • Extended the active session history functionality:

    • Added the ability to manage profile parameters, as well as clear and download profile data. The data is downloaded in a raw non-aggregated form to be used as a source in external systems.

    • Added the ability to view original prepared statements, not just related EXECUTE statements.

    • Added navigation from active session history to SQL statistics by query ID.

    • Improved the active session history interface with better filters, units of measurement, graph visualizations, and default interval selection.

    For more information, refer to Section 57.1.4, Section 57.1.5, Section 57.2.1, Section 57.2.2, and Chapter 57.

  • Implemented the mutual TLS (mTLS) authentication scheme in addition to the authentication via API keys, so both agent and manager can verify the related party when establishing an HTTPS connection.

    For more information, refer to Section 7.5, and the manager and agent configuration file descriptions.

PPEM 2.9 also includes the following functional upgrades and improvements:

  • Task and backup management.

    Added the ability to reassign tasks and rebind a backup storage for instances to be deleted.

    For more information, refer to Section 40.11 and Section 41.5.6.

  • BiHA clusters.

    Added the ability to manage the minimum number of healthy nodes in the cluster when creating, editing, and changing the topology of a BiHA cluster.

    For more information, refer to Section 41.1.2 and Section 41.1.4.

  • Metric storages.

    Added the ability to delete linked triggers when deleting a metric storage.

    For more information, refer to Section 31.4.2.

  • Audit event log.

    Optimized the audit event log:

    • Changed the format of the message_id field in audit events to UUID v7.

    • Added the user_unblock audit event type to track when a user is unblocked.

    • Changed the default syslog message tag for audit events from ppem to AUDIT.

    For PPEM to log audit events, the logging must be configured first in the ppem-manager.yml manager configuration file. For more information, refer to Section 7.8 and the manager configuration file description.

  • Task creation.

    Added the ability to specify the Description parameter when creating tasks for database reindexing, vacuuming, and planner statistics collection, as well as creating snapshot schedules, backup schedules, and housekeeping rules.

    For more information, refer to Section 44.6, Section 44.8, Section 44.4, Section 62.4.1, Section 67.5.1, and Section 58.1.

  • Instance management.

    Added the ability to view detailed error information about an instance.

    For more information, refer to Section 40.2.

  • Repository maintenance.

    Added the ability to manually truncate tables specified in housekeeping rules to avoid out-of-space server crashes.

    For more information, refer to Section 58.6.

  • The manager and agent configuration files.

    Added the autodiscovery.instance_name_template parameter to the manager and agent configuration files. This parameter allows specifying a custom naming template for automatically discovered instances.

    For more information, refer to the manager and agent configuration file descriptions.

  • User interface.

    Redesigned the monitoring section, the instance creation form, and improved status display in the instance and task tables.

    For more information, refer to Section 51.1, Section 40.1, Section 40.2, and Section 66.1.

  • Upgraded Go to version 1.26.6.

  • Security.

    Fixed a number of common vulnerabilities and exposures (CVEs) to improve overall solution security and protect against potential attacks. It is recommended to upgrade to the latest version to mitigate potential risks.