Percona Monitoring and Management 1.8.0 Is Now Available

The latest release of Percona Monitoring and Management (PMM) 1.8.0 is available as of February 27, 2018.

Percona Monitoring and Management is a free and open-source platform for managing and monitoring MySQL and MongoDB performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL and MongoDB servers to ensure that your data works as efficiently as possible.

This release introduces many improvements in the user interface and optimizations of performance.

New landing page

The home page has been removed in favor of the Home dashboard to make the look and feel of PMM web interface more consistent. The Home dashboard gives a general overview of your system and provides links to useful resources. You can immediately go to a dashboard of your choice either by using the conventional Dashboard drop down at the top of the page or the new dashboard menu.

[IMG2=JSON]{“data-align”:“none”,“data-size”:“full”,“src”:“https://www.percona.com/blog/wp-content/uploads/2018/02/home.png”}[/IMG2]Improved dashboard menu layout

The new dashboard menu provides a convenient grouping of dashboards making the switching between dashboards easy: select a group, such as MySQL or OS, and choose from a short list in the menu that opens. The new dashboard menu is available from every dashboard in PMM.

[IMG2=JSON]{“data-align”:“none”,“data-size”:“full”,“src”:“https://www.percona.com/blog/wp-content/uploads/2018/02/metrics-monitor.menu_.png”}[/IMG2]

Memory improvements

This release also features improved memory usage on the host system in PMM Server. By default PMM now automatically scales its use with system size rather than using static amount of memory, unless you explicitly set the maximum value (by using the METRICS_MEMORY option in Docker, for example).

New Features
[LIST]
[]PMM-1145: Move Percona Dashboards to Grafana Plugin
We have updated the Percona Dashboards to use the Grafana Plugins system in order to simplify upgrades.
[
]PMM-1470: Implement a Custom Prometheus rds_exporter to Collect Amazon CloudWatch Metrics
You can now explore CloudWatch metrics from Prometheus, for example using the Advanced Data Exploration dashboard. In prior versions we were using CloudWatch API calls directly.
[]PMM-2046: Configure Memory Consumption Automatically for PMM Server
In this release we improved memory usage in PMM Server. By default PMM now automatically scales its use with system size rather than using static amount of memory. You can override this behaviour, for example if you need to share resources with other containers by using the METRICS_MEMORY option in Docker. You can use the old static size of memory by running: [TABLE]
[TR]
[TD]1[/TD]
[TD]docker … -e METRICS_MEMORY=786432[/TD]
[/TR]
[/TABLE]
[/LIST]Improvements
[LIST]
[
]PMM-1425: Replace the Home Page with the Home Dashboard
The home page has been removed in favor of the Home dashboard to make the look and feel of PMM web interface more consistent. The Home dashboard gives a general overview of your system and provides links to useful resources. You can immediately go to a dashboard of your choice either by using the conventional Dashboard drop down at the top of the page or the new dashboard menu.
[]PMM-1738: Add a Dashboard Menu and Make the Discovery of Dashboards Easier
[
]PMM-1976: Apply Consistent Rules for Computing CPU Metrics
We updated the query that generates CPU utilization for the MySQL Overview, Summary and System Overview Dashboards as before we were being in-consistent in our determination of CPU.
[]PMM-2007: Squash New Docker Layers for Smaller Total Size
We reduced the size of the Docker container from ~475 MB to ~350 MB
[
]PMM-1711: Add SQL and External Locks graphs to MySQL Performance Schema dashboard
Added new graph to the PERFORMANCE SCHEMA dashboard to show locks from perspective of count of events and from time.[IMG2=JSON]{“data-align”:“none”,“data-size”:“full”,“src”:“https://www.percona.com/blog/wp-content/uploads/2018/02/graph-1024x174.png”}[/IMG2]
[/LIST]
[LIST]
[]PMM-1763: Update the Forked Prometheus Exporter mysqld_exporter to the Latest Upstream Version to Include Recent Bug Fixes
The mysqld_exporter has been updated to the latest upstream prometheus/mysqld_exporter to include recent bug fixes.
[
]PMM-2004: Add /ping alias to nginx
Added basic health check URL to the API for PMM Server.
[]PMM-1365: Provide Descriptions of All Metrics in the Cross Server Graphs Dashboard
We have added metric descriptions in order to improve understanding of the displayed metric series and to provide links to documentation/blog articles, beginning with the Cross Server Dashboard. [IMG2=JSON]{“data-align”:“none”,“data-size”:“full”,“src”:“https://www.percona.com/blog/wp-content/uploads/2018/02/cross-server-description.png”}[/IMG2]
[/LIST]
[LIST]
[
]PMM-1343: Provide Descriptions of All Metrics in the Summary Dashboard
[]PMM-1364: Provide Descriptions of All Metrics in the MySQL InnoDB Metrics Dashboard
[
]PMM-1994: Provide Descriptions of All Metrics in the MySQL Amazon Aurora Dashboard
[]PMM-1922: PMM-server as instance for all components on Server
[
]PMM-2005: Upgrade Orchestrator to the Latest Stable Release
[]PMM-1957: Build Go 1.9.4
Updated Go to 1.9.4 which resolves a security problem in the go get command (For more information, see Golang issue #23672)
[/LIST]Bug Fixes
[LIST]
[
]PMM-2124: The Number of the New Version Is Missing in the Notification of the Successful Update of PMM
[]PMM-1453: MySQLD Exporter wrong mapping of innodb_buffer_pool_pages
[
]PMM-2029: Deadlock when adding external exporter
[]PMM-1908: RDS MySQL nodes do not display Current QPS
[
]PMM-2100: rds_exporter Crashed after Running for Several Minutes
[]PMM-1511: PXC Cluster Is Not Recognized Correctly When MariaDB Nodes Are Monitored
[
]PMM-1715: MongoDB QAN: Wrong Per Query Stats:
[]PMM-1893: In QAN, the Tables Element Can Be Empty
[
]PMM-1941: Fingerprint storage bug
[]PMM-1933: If some parts of collector got error, whole collector is down
[
]PMM-1934: mysqld_exporter/collector/info_schema_auto_increment.go fails if there are same table names but with different cases
[*]PMM-1951: Regression in pmm-admin add mysql:queries only – not working
[/LIST]