Percona Monitoring and Management 2.44.1¶

Release date	April 24, 2025
Installation	- Install Percona Monitoring and Management 2 - Install Percona Monitoring and Management 3

Percona Monitoring and Management (PMM) is an open source database monitoring, management, and observability solution for MySQL, PostgreSQL, and MongoDB.

It enables you to observe the health of your database systems, explore new patterns in their behavior, troubleshoot them, and execute database management operations regardless of whether your databases are located on-premises or in the cloud.

Release summary¶

PMM 2.44.1 is a maintenance release that improves MongoDB monitoring reliability and addresses security vulnerabilities through updated Docker images.

What’s new¶

PMM v3 migration notice¶

When you launch PMM 2, you’ll now see a notification prompting you to migrate to PMM v3, as PMM 2 is no longer actively developed. Since the release of PMM 3 in January 2025, PMM 2 in maintenance phase, receiving only Critical and High CVE fixes until July 30, 2025. For continued support and to access all future improvements, we strongly recommend upgrading to PMM 3 now.

Moving to PMM v3 provides significantly enhanced security, improved stability, and an overall smoother user experience. You will now be presented with a direct link to the migration documentation to help guide you through the process.

Fixed visibility of offline MongoDB replica set nodes¶

Fixed a monitoring gap in the MongoDB ReplSet Summary dashboard, where nodes in a Down state occasionally disappeared from the States panel.

Offline now remain consistently visible in both panels with a clear Down status (highlighted in red).

CVE fixes¶

Fixed CVE-2023-45288, a Server-Side Request Forgery (SSRF) vulnerability, by updating the golang.org/x/net/http/httpproxy package to version 0.36.0 across multiple components in the PMM Client Docker image.

This prevents potential attacks that could bypass proxy restrictions and strengthens overall security.

Known issues¶

PMM ProxySQL monitoring impacted by exporter status error¶

The ProxySQL exporter transitions to the Done status instead of Running after being added for monitoring. This leads to the exporter failing to collect metrics from your ProxySQL instances, which means that PMM cannot accurately track ProxySQL performance and identify potential issues.

A fix for this issue is planned for a future PMM 2 release. Alternatively, you can upgrade to PMM 3, where the ProxySQL exporter works as expected.

PostgreSQL Query Analytics with `pg_stat_monitor`¶

When using pg_stat_monitor extension with pg_stat_monitor.pgsm_enable_query_plan enabled, Query Analytics (QAN) displays incorrect execution times that can be off by 1000x or more. For example, simple SELECT queries that should complete in milliseconds may appear to take 50,000+ seconds.

This is because enabling query plans causes pg_stat_monitor to create multiple records for each query, leading to incorrect timing calculations.

Workaround: Disable query plan collection to restore accurate timing metrics:

    -- Check current setting
    SHOW pg_stat_monitor.pgsm_enable_query_plan;

    -- Disable query plan collection
    ALTER SYSTEM SET pg_stat_monitor.pgsm_enable_query_plan = off;
    SELECT pg_reload_conf();

    -- Verify the change
    SHOW pg_stat_monitor.pgsm_enable_query_plan;