Skip to content

Percona Monitoring and Management 2.25.0

Date: December 14, 2021
Installation: Installing Percona Monitoring and Management

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance.

Important note for users considering docker way upgrade to PMM 2.25.0

If you upgrade from a PMM version less than or equal to 2.23.0 using docker, it will fail if your PMM does not have external access (access to repo. Thus, it is recommended to upgrade to PMM 2.26.0 instead. See PMM-9416 for more details.

Release Highlights

  • Percona Platform (Technology Preview):

    • Connect Percona Monitoring and Management (PMM) to Percona Platform to boost the monitoring capabilities of your PMM installations and access all your Percona accounts and services from one single, centralized location. For more information, see the Percona Platform Portal documentation
  • Enhanced PostgreSQL monitoring

    • You can now specify custom database names when adding PostgreSQL Servers for monitoring. Previous PMM versions always used the default postgres name instead.

    • Added support for the new version of pg_stat_monitor extension. Release Candidate v1.0.0-rc.1 brings many new PostgreSQL metrics, Dashboards and Query Analytics! To find out about all the features available in the new pg_stat_monitor version, see the pg_stat_monitor User guide

    • Added compatibility for the latest Percona Distributions for PostgreSQL 14, 13, 12, 11 updated on December 7, 2021, which includes the newest version of the pg_stat_monitor extension.

  • Grafana usability enhancements

    • PMM is now using the native Grafana provisioning mechanism for adding dashboards, plug-ins, and data sources. This ensures faster and more reliable upgrading to newer PMM versions. Your existing plug-ins and dashboard changes are preserved during upgrades, but always make sure to back them up before upgrading and check that everything transferred correctly afterward.

    • Added option to change the time zone on dashboards. This selection is preserved while you navigate over Dashboards. If you need to change this setting permanently for your account, change it in your preferences by the URL: https://YOUR_PMM_SERVER/graph/profile

  • DBaaS (Technical Preview)

    • You can now deploy and update your DBaaS created PXC clusters to the latest version of Percona Distribution for MySQL Operator 1.9.0. This enables you to take advantage of the latest features and fixes.
  • PMM environment enhancements

    • The pmm-client docker container can now be started as a sidecar. For users that use PMM client in Kubernetes or build automation around it, you can now start the client as a sidecar container simply by passing a flag. The client will also gracefully handle any instances where the connection to DB is not available. For more details, see the PMM Client documentation

    • Removed support for Ubuntu 16.04. With the support of new products and new versions of already supported products, we also removed old, unsupported software. As of this release, we are no longer supporting Ubuntu 16.04 in PMM according to recent announcements

New Features

  • PMM-9050: Connect PMM Server to Percona Platform for additional account info in PMM and value added content


  • PMM-8545: DBaaS: Support of Percona Distribution for MySQL Operator 1.9.0 in PMM
  • PMM-7677: Docker container for pmm-client: Option to change behavior and follow sidecar pattern The flags PMM_AGENT_SIDECAR and PMM_AGENT_SIDECAR_SLEEP does this. Read more in documentation
  • PMM-3516: Optimize provisioning mechanism of plugins, dashboards, and data sources in PMM
  • PMM-8674: Integrated Alerting: Add Tooltips to Add Alert Rule fields to make it easier to understand what information is needed
  • PMM-8505: Integrated Alerting: Clarify description of the ‘Low memory’ Alert Template
  • PMM-8503: Integrated Alerting: Field validation in Email and Slack tabs when updating settings
  • PMM-7527: Integrated Alerting: Improvements to overall user experience for action buttons in Alerting
  • PMM-7079: Integrated Alerting: New ‘information’ icon to give additional details about Alerts without cluttering screen
  • PMM-8259: Better clarification of error messages in pmm-admin when PMM server can’t be unregistered
  • PMM-8972: Add ability to specify custom base path to exporters and tools using pmm-admin command
  • PMM-8282: Improved messaging for TLS option when adding Remote instances in PMM over UI

Bugs Fixed

  • PMM-9169: Security Advisor Checks are not working for MongoDB instances
  • PMM-8982: Backup Management: User is not able to see MongoDB backup logs if backup was taken on older version of pmm-server
  • PMM-9157: Dashboards: Changing the timezone on dashboards does not persist navigation
  • PMM-7116: Dashboards: Incorrect STARTUP state on MongoDB ReplSet Summary dashboard
  • PMM-8993: Integrated Alerting: Sending email using Gmail fails
  • PMM-7802: PMM can’t monitor MongoDB arbiter nodes (Thanks to Artem Meshcheryakov for reporting this issue)
  • PMM-6937: Can’t add PostgreSQL instances to PMM without postgres DB in PostgreSQL server (Thanks to Daniel Kowalewski for reporting this issue)
  • PMM-7447: Can’t add into PMM instances of PostgreSQL with SCRAM-SHA-256 authentication
  • PMM-9085: PMM Server crashes after upgrading to 2.22 every 4 hours
  • PMM-9156: pmm-agent paths-base option not working for pmm2-client binary installation in PMM 2.23.0
  • PMM-8461: DBaaS: Confusing error when accessing DBaaS pages when it’s disabled
  • PMM-8110: DBaaS: Registering K8s cluster with operators already installed can cause error
  • PMM-8694: Query Analytics: URLs in Query Analytics with a selected query and a timestamp range does not select the query
  • PMM-9227: Pagination Reset on QAN after Time Range change doesn’t work, results in wrong results
  • PMM-9298: PMM AMI image in 2.24.0 has only 8GB space for data and Volume Size Check fails while upgrading to 2.25.0

Important note for users of PMM 2.24.0

2.24.0 AMI image has only 8GB available for the data, it is a bug (see PMM-9298). To resize a disk to full size you need to login to AMI instance with SSH and use the following command:

curl -o lvn-fix.yml && sudo ansible-playbook lvn-fix.yml

For instructions about how to access your instances by using an SSH client, see Connecting to Your Linux Instance Using SSH Make sure to replace the user name ec2-user used in this document with admin.

What this command does:

  1. Downloads Ansible playbook and runs it
  2. Copy your data from /srv to the temporary directory
  3. Create lvm partition
  4. Copy data from system disk to a new LVM partition

Known issues

  • PMM-9255: After connecting PMM to Percona Platform, PMM occasionally shows a false permission issue notification, incorrectly suggesting that the connection could not be established due to missing permissions. Reload the page to remove the incorrect notification and confirm the connection.
  • PMM-9312: It’s not possible to enable collStats, indexStats and -max-collections-limit for MongoDB

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.

Last update: 2024-06-12