Configuration presets management.

Added centralized management of configuration presets to meet your organization's internal standards and requirements on information security and information system workload.

This functionality is in the beta phase and has limitations. It will be expanded and updated in further releases.

For more information, refer to Section 5.7.

Mass instance operations.

Added the ability to perform an operation on multiple instances at once.

This functionality is in the beta phase and has limitations. It will be expanded and updated in further releases.

For more information, refer to Section 5.27.3.

Alerts and triggers.

Added the ability to send alerts to users and user groups via email based on alert triggers. Alert triggers fire when values of metrics are below, equal to, or higher than the thresholds specified in alert trigger rules.

This functionality is in the beta phase and has limitations. It will be expanded and updated in further releases.

For more information, refer to Section 5.17.

Repository maintenance.

Implemented automatic cleaning of the repository database tables to keep them from overflowing using housekeeping rules. Housekeeping rules clean tables when data is stored longer than the specified time and when certain conditions are met. Tables can also be cleaned at the specified time interval.

Housekeeping rules are especially relevant if you store instance logs and metrics in the repository database.

This functionality is in the beta phase and has limitations. It will be expanded and updated in further releases.

For more information, refer to Section 5.20.

BiHA cluster management.

Added centralized management of BiHA clusters and their nodes.

For more information, refer to Section 5.6.

User role management.

Added centralized management of user roles based on the existing privileges according to your organization's requirements on information security and privilege hierarchy.

For more information, refer to Section 5.4.3.

Automatic user blocking.

Implemented automatic blocking of users after the specified number of failed attempts to log in to the web application. Users blocked due to too many failed log-in attempts are not unblocked automatically.

For more information, refer to Configuring the Automatic User Blocking.

Request tracing.

Added the ability to trace incoming requests to the manager and agents. Tracing data is exported from PPEM using OTLP (OpenTelemetry protocol) and sent to a receiver supporting OTLP.

For more information, refer to Section 4.9.

Connecting to instances via SSL.

Added the ability for the manager and agents to connect to instances via SSL.

For more information, refer to Section 4.8.

Request proxy.

Added the ability to proxy requests to PPEM based on URL prefixes.

For more information, refer to Section 4.10.

PostgreSQL 18 is supported.

The manager and agents can now manage PostgreSQL 18 DBMS.

Metrics storage model optimization.

Switched the repository database to the flat metrics storage model. The new model is less resource-intensive and less susceptible to deadlocks.

Updated Section 1.5.

Added information on limitations to Section 4.1.

Added Section 1.2.6.

This section explains how agents collect instance data and send it to the manager for post-processing.