Percona Monitoring and Management 2.3.0

Date:	February 19, 2020

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

For PMM install instructions, see Installing PMM Server and Installing PMM Client.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

Improvements and new features

PMM-5064 and PMM-5065: Starting from this release, users will be able to integrate PMM with an external Alertmanager by specifying the Alertmanager URL and the Alert Rules to be executed inside the PMM server (This feature is for advanced users only at this point)
PMM-4954: Query Analytics dashboard now shows units both in the list of queries in a summary table and in the Details section to ease understanding of the presented data
PMM-5179: Relations between metrics are now specified in the Query Analytics Details section
PMM-5115: The CPU frequency and temperature graphs were added to the CPU Utilization dashboard
PMM-5394: A special treatment for the node-related dashboards was implemented for the situations when the data resolution change causes new metrics to be generated for existing nodes and services, to make graphs show continuous lines of the same colors

PMM-4620: The high CPU usage by the pmm-agent process related to MongoDB Query Analytics was fixed
PMM-5377: singlestats showing percentage had sparklines scaled vertically along with the graph swing, which made it difficult to visually notice the difference between neighboring singlestats.
PMM-5204: Changing resolution on the PMM settings page was breaking some singlestats on the Home and MySQL Overview dashboards
PMM-5251: Vertical scroll bars on the graph elements were not allowed to do a full scroll, making last rows of the legend unavailable for some graphs
PMM-5410: The “Available Downtime before SST Required” chart on the PXC/Galera Node Summary dashboard was not showing data because it was unable to use metrics available with different scraping intervals