Skip to content
PERCONA MONITORING AND MANAGEMENT DOCUMENTATION

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Monitoring and Management 3.9.0

Release date: July 2026

Percona Monitoring and Management (PMM) is an open source database monitoring, management, and observability solution for MySQL, PostgreSQL, MongoDB, Valkey and Redis. PMM empowers you to:

  • monitor the health and performance of your database systems
  • identify patterns and trends in database behavior
  • diagnose and resolve issues faster with actionable insights
  • manage databases across on-premises, cloud, and hybrid environments

📋 Release summary

Note

Release summary to be added.

🔒 Security updates

Removed provisioned PostgreSQL datasource (PMM-15139)

PMM no longer includes a preconfigured PostgreSQL datasource for internal dashboard panels.

This change prevents authenticated users, including users with the Viewer role, from using the datasource to run arbitrary or destructive SQL queries against PMM’s internal database.

Since the Grafana PostgreSQL datasource does not support a read-only mode, removing the provisioned datasource is the most effective way to eliminate this risk. If you need it, you can add it manually.

This update completes the security hardening that began in PMM 3.7.0, which addressed a remote code execution vulnerability in the same datasource (CVE-2026-25212).

Data size monitoring for MongoDB replica sets and sharded clusters

You can now monitor data growth across your MongoDB deployments and plan capacity from the MongoDB ReplSet Summary and MongoDB Sharded Cluster Summary dashboards. Each dashboard includes two new panels for tracking data size:

  • Total data size: shows how much space your data and indexes currently occupy, so you know exactly where your deployment stands at any point in time.
  • Data size over time: plots the same total over the selected time range, so you can spot growth trends and make informed capacity decisions.

These panels require the dbstats collector on the MongoDB exporter. To enable it, pass --enable-all-collectors when adding your MongoDB service with pmm-admin add mongodb, or update an existing service with pmm-admin inventory change agent.

Disable individual metric collectors per service

PMM 3.9.0 adds a Disable collectors field to the Add service form for MySQL, PostgreSQL, MongoDB, and ProxySQL. You can now exclude specific metric collectors from collection without removing the service or modifying the exporter configuration.

This is useful when certain collectors generate metrics you don’t need, add overhead on resource-constrained hosts, or cause issues with specific database configurations.

Disable collectors field in Additional options

To use it, go to PMM Configuration > Add Service, expand Additional options, and enter a comma-separated list of collector names in the Disable collectors field.

For the full list of available collectors per database type, see Connect MySQL databases to PMM and Connect PostgreSQL databases to PMM.

📈 Improvements

  • PMM-13306: Added data size panels to the MongoDB ReplSet Summary and MongoDB Sharded Cluster Summary dashboards to help you monitor data growth and plan capacity.

  • PMM-14502: Added a dedicated topic for running custom queries on MySQL so that you can collect any MySQL metric accessible via SQL and monitor it in PMM alongside your standard dashboards.

✅ Fixed issues

  • PMM-14661: Fixed PMM Server becoming unresponsive when viewing stored metrics in Query Analytics for data older than one week.

  • PMM-15029: Fixed an issue where the auto-generated PostgreSQL password for PMM HA could contain : or @ characters, producing an invalid URI and preventing Grafana from connecting to the database on startup.

  • PMM-15030: Fixed missing metrics data when PMM is configured to use an external VictoriaMetrics instance via PMM_VM_URL. If you saw gaps in your dashboards or vmagent errors after setting this variable, this fix resolves the issue.

  • PMM-14576: Fixed an issue where MongoDB backups completed successfully in PBM but PMM failed to detect this, reporting them as failed in the Status column on the Backup > All Backups page.

  • PMM-14193, PMM-15145: Fixed the built-in MySQL Down, MongoDB Down, PostgreSQL Down, Valkey Down, and Redis Down alerts incorrectly resolving to Normal when both the database and its PMM agent go down at the same time. The alert now correctly stays in Firing state even when metrics stop being reported.

  • PMM-14519: Fixed MySQL services failing to connect when --tls-skip-verify was set on a database server with TLS disabled. PMM incorrectly treated tls_skip_verify: true as a request to use TLS, causing the agent to report TLS requested but server does not support TLS and stop collecting metrics.

  • PMM-13910: Fixed Top Hottest Collections by Read and Top Hottest Collections by Write panels in the MongoDB Sharded Cluster Summary and MongoDB Collections Overview dashboards showing only internal collections instead of the busiest user collections.

  • PMM-14193, PMM-15145: Fixed built-in MySQL Down, MongoDB Down, PostgreSQL Down, Valkey Down, and Redis Down alerts incorrectly resolving to Normal when the monitored database service and its PMM agent went down at the same time. These alerts now correctly remain in Firing state when database availability metrics stop being reported.

  • PMM-15118: Fixed the Oplog GB/Hour panels in the MongoDB ReplSet Summary, MongoDB Sharded Cluster Summary, and MongoDB Oplog Details dashboards showing an empty metric name in the legend instead of the service name.

  • PMM-15114: Fixed the Scanned and Moved Objects panel in the MongoDB Instance Summary dashboard showing blank labels in the legend instead of the operation type (scanned, scanned_objects).