v2.43.2

Percona Monitoring and Management 2.43.2

Release date	October 30th, 2024
Installation	Installing Percona Monitoring and Management

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.

PostgreSQL 17 support for Query Analytics (QAN)

This patch release adds PostgreSQL 17 support for Query Analytics with updates to the pg_stat_statements and pg_stat_monitor extensions.

To align with PostgreSQL 17 standards, we've renamed the blk_read_time field to shared_blk_read_time and the blk_write_time field to shared_blk_write_time.

All dashboards reflect these changes, and the API supports both old and new field names, for backward compatibility.

Secure Grafana image rendering

PMM Server now supports secure Grafana image rendering capabilities through a dedicated container deployment, providing isolated rendering operations without impacting PMM Server resources.

Previously installed directly within PMM Server, the Grafana Image Renderer plugin now runs in a separate container, offering secure HTTPS communication and custom CA certificate configuration through the PMM API.

To update the plugin installation:

1. Deploy the Grafana Image Renderer container (grafana/grafana-image-renderer:latest) alongside PMM Server within the same Docker network.

2. Configure PMM Server with the following environment variables, where renderer is the hostname of the Grafana Image Renderer container, and pmm-server is the hostname of PMM Server within the Docker network:

   • GF_RENDERING_SERVER_URL=http://renderer:8081/render
   • GF_RENDERING_CALLBACK_URL=https://pmm-server:8443/graph/

Fixed: High memory consumption in MongoDB exporter

We have updated the MongoDB exporter to address a critical issue present in version 2.43.1 where unclosed connections led to increasingly high memory consumption over time.

This resolves the Failed to get PBM configuration error, the users may have encountered as a result of the memory leak, and significantly reduces the rate of increase in total memory allocations.

v2.43.1

Percona Monitoring and Management 2.43.1

Release date	October 2nd, 2024
Installation	Installing Percona Monitoring and Management

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.

Fixed issue: PMM 2.43.0 upgrade failure

This release addresses the upgrade failure to PMM 2.43.0 via the UI. The issue affected PMM Servers running versions prior to 2.43.0, where an outdated version of percona-release resulted in a missing percona-telemetry-agent package during the PostgreSQL 14 upgrade process.

Resolution

Upgrading directly to PMM 2.43.1 will bypass this issue entirely.

Workaround for ongoing 2.43.0 upgrades

If you've already initiated an upgrade to 2.43.0 and wish to complete this specific installation, follow the workaround below for Docker installations:

Before retrying the upgrade run docker exec -t pmm-server dnf clean all, then proceed with the 2.43.0 upgrade.

This command refreshes package metadata, resolving dependency issues and allowing the upgrade to proceed smoothly.

v2.43.0

Percona Monitoring and Management 2.43.0

Release date	September 19th, 2024
Installation	Installing Percona Monitoring and Management

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.

What's new in this release

PMM 2.43 brings a host of updates, including new and redesigned dashboards, new collectors and metrics, enhanced troubleshooting capabilities, strengthened security, and initial steps towards expanded platform support with experimental ARM compatibility for PMM Client.

Additionally, this release features many bug fixes and performance enhancements to improve your user experience.

MongoDB dashboard improvements and GA of recent experimental dashboard

We've made some significant enhancements to MongoDB monitoring, focusing on redesigned dashboards, streamlined navigation, and general availability (GA) of previously experimental dashboards.

Redesigned dashboards

We've overhauled two critical MongoDB dashboards to provide more value, especially for complex, multi-environment setups:

• Replica Set Summary
• Sharded Cluster Summary (formerly Cluster Summary)

These dashboards now offer enhanced usability, improved insights, and optimized visualizations for complex environments.

They focus on highlighting potential database issues for faster resolution and provide centralized, actionable insights without clutter.

General availability of Experimental dashboards

The redesigned dashboards, along with the following previously experimental dashboards, are now generally available:

• MongoDB Oplog Details
• MongoDB Collection Overview
• Replica Set Summary
• Sharded Cluster Summary (formerly Cluster Summary)

📝 Experimental vs. GA
Experimental dashboards are newly developed or redesigned dashboards that are initially released as preview features. Once these dashboards have proven their value and stability, they are transitioned to GA status, which indicates that they are fully stable and ready for general use.

New experimental MongoDB Router Summary dashboard

We've created a new experimental MongoDB Router Summary dashboard to enhance your experience when monitoring MongoS (routers) of MongoDB sharded clusters.

This dashboard provides:

• MongoS availability (UP or DOWN) with a chart showing the state of all MongoS instances, similar to the Replica Set Summary dashboard
• MongoS version
• CPU, Memory, Disk metrics, and much more

To access the new dashboard, go to MongoDB> High availability > Router summary.

Accessing the new dashboards

You can find the updated dashboards in the MongoDB and Dashboards sections of the main menu. They replace the previous versions as the default dashboards for MongoDB monitoring.

The old dashboards have been moved to the Experimental folder and renamed with (Old) appended to their names. Future releases will remove these older versions.

Updated MongoDB menu structure

To complement the dashboard improvements, we've also restructured the MongoDB section on the main menu for better navigation and accessibility:

• reorganized menu for a more intuitive navigation, prioritizing the two updated GA dashboards above.

• decluttered view by moving older dashboards to the Experimental folder or removing them from the menu.

• added MongoDB Instance Summary, Collection Overview and MongoDB Oplog Details the main menu:

  

We encourage you to start using the new dashboards to benefit from their enhanced monitoring capabilities. We also invite you to share your feedback in the PMM forum so we can continue to improve them.

New MongoDB collector: CurrentOp

The MongoDB exporter now includes the CurrentOp collector, offering visibility into active operations, including the new mongodb_currentop_query_uptime metric.

To start the MongoDB exporter with the CurrentOp collector enabled, use the --enable-all-collectors flag when adding MongoDB services to your PMM instance:

pmm-admin add mongodb --enable-all-collectors ...

Specifying a limit with --max-collections for this collector is not necessary.

For more information on MongoDB collectors and metrics, see the pmm-admin commands documentation.

Note

Operation collection limitation

To minimize impact on disk usage, the CurrentOp collector is designed to collect only operations that have been running for longer than 1 minute. This limitation helps focus on potentially problematic long-running operations while keeping data volume manageable.

Monitoring Percona Backup for MongoDB (PBM)

PMM now supports monitoring Percona Backup for MongoDB (PBM) setups through a dedicated collector in the MongoDB exporter, providing key insights into pbm-agent statuses, PITR configuration, and backup statuses.

New metrics for this include:

• mongodb_pbm_cluster_backup_configured: indicates if PBM is configured for the cluster (1 = configured, 0 = not configured).

• mongodb_pbm_agent_status: shows the status of each PBM agent connected to the cluster nodes (0 = functioning, ≥1 = down, e.g., 2 for unreachable agents).

• mongodb_pbm_cluster_pitr_backup_enabled: specifies whether PITR is enabled in the current PBM configuration (1 = enabled, 0 = not enabled).

• mongodb_pbm_backup_size_bytes: displays the size of each backup in PBM's history, with labels for operation ID (opid), status (status), and backup name (name).

• mongodb_pbm_backup_duration_seconds: shows the duration of each PBM backup operation, using the same labels as mongodb_pbm_backup_size.

These metrics are enabled by default, so if you’re already using PBM, you’ll automatically start receiving them. To access them, go to Explore > Metrics, search for mongodb_pbm, and run your query.

This is just the beginning! While you can create custom dashboards with these metrics, we’re developing dedicated PBM dashboards for a quick overview of your backup status, along with alert templates to help you proactively monitor your PBM setup.

Improved troubleshooting

We've enhanced PMM's troubleshooting capabilities to provide you with better insights and more efficient problem-solving tools:

Enhanced PMM Server logs

The default number of log lines for each log file returned by https://<pmm-server>/logs.zip endpoint has been increased from 1,000 to 50,000.

Additionally, the endpoint now includes a customizable line-count parameter in the download URL, allowing you to specify a custom number of log lines or opt for unlimited log size. For more information, see the API documentation.

Streamlined Kubernetes diagnostics

New PMM Client Docker images now include essential troubleshooting tools:

• tar enables easier file transfer in and out of containers using the kubectl cp command.
• curl allows direct checking of exporters to verify their proper functioning.

Improved security

This update addresses several security issues related to the GNU C Library (Glibc), specifically affecting the Name Service Cache Daemon (nscd). Additionally, it resolves multiple security vulnerabilities by upgrading various third-party packages.

Important changes to PMM Update process

To ensure you can access the most up-to-date and secure versions, we've implemented two key changes to the update process:

Transition to a dedicated repository

Since July 1st 2024, PMM updates are distributed exclusively through the dedicated repo.percona.com/pmm2-client repository.

To smoothly transition to this repository and verify that your system is correctly configured, download and run our automated script from GitHub: check_percona_packages.py.

For detailed instructions and more information about this change, read our recent blog post Ensure the Correct Repositories are Enabled for Percona Packages and updated installation instructions.

Update process for older PMM versions

If you’re using PMM version 2.38 or earlier, you might encounter issues when updating to the latest version via the UI Update button. These issues arise due to Red Hat's discontinuation of CentOS 7 repositories, which impacts PMM installations based on CentOS 7.

To ensure your PMM installation continues to receive updates and transitions smoothly away from the discontinued CentOS 7 base:

• for Docker instances: perform a one-time [Docker update](h...

v2.42.0

Percona Monitoring and Management 2.42.0

Release date	June 11th, 2024
Installation	Installing Percona Monitoring and Management

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.

What's new in this release

This release introduces support for Ubuntu 24.04, configurable metrics resolutions per service, improved connection management for PostgreSQL and PMM Agent, and experimental dashboards for PMM self-monitoring and MongoDB.

The release also brings enhancements to MySQL Query Response Time Details, adds new metrics and labels for PostgreSQL, and addresses several issues related to MongoDB monitoring, upgrades, and Query Analytics and High Availability documentation.

Experimental dashboards in PMM are new or redesigned dashboards that are released as a preview feature for you to test and provide feedback, as we hope to include them as defaults in a future release.

Keep in mind that these dashboards are not considered fully stable or complete, and their design, functionality, and metrics may change in future releases based on user feedback and further development.

Release highlights

Ubuntu 24.04 Noble Numbat support

PMM now officially supports monitoring of databases running on the recently released Ubuntu 24.04 Noble Numbat operating system.

With this addition, PMM continues to provide comprehensive coverage across a wide range of Linux distributions commonly used in database deployments.

Check the full list of supported platforms on the Percona Software Support Lifecycle webpage.

For information on installing the PMM Client on Linux, see Set up PMM Client.

Configurable metrics resolutions per service

You can now configure metrics resolutions on a per-service basis by setting Low-Resolution (LR), Medium-Resolution (MR), and High-Resolution (HR) settings for each exporter individually.

Customizing the resolution settings for individual services means that you can fine-tune your PMM setup to balance data granularity and resource consumption. This will enable you to:

• allocate resources efficiently by focusing on high-resolution data for key services
• reduce storage requirements by adjusting resolution for less critical components
• align your monitoring setup with the specific needs of your environment

This feature is currently accessible via the PMM API and will be integrated into the user interface in a future release.

API call example:
sh curl --request POST \ --url https://<your-pmm-address>/v1/inventory/Agents/ChangePostgresExporter \ --header 'accept: application/json' \ --header 'content-type: application/json' \ --data ' { "common": { "metrics_resolutions": { "hr": "60s", "mr": "300s", "lr": "3600s" } }, "agent_id": "<agent-id>" } '

Improved connection management for PostgreSQL Services and pmm-agent

PMM now offers enhanced connection management capabilities for PostgreSQL services and the PMM Agent, to optimize resource utilization and prevent potential performance issues caused by excessive connections.

PostgreSQL services

When adding a new PostgreSQL services, you can now set a maximum limit on the number of connections that the PostgreSQL exporter can open to the same PostgreSQL instance.

This feature, previously available only through the CLI, is now also accessible through the PMM web interface as well:

• PostgreSQL service: PMM Configuration > Add Service > PostgreSQL > Configuring PostgreSQL Service
• RDS PostgreSQL service: PMM Configuration > Add Service > Amazon RDS > Discover with Amazon Credentials > RDS PostgreSQL

By setting a maximum connection limit, you can prevent excessive connections during concurrent operations, and ensure that connections are closed promptly to avoid idle connections.

When adjusting the maximum number of connections, consider the following:

• higher values might be needed for larger or busier instances.
• setting the limit too high can impact performance.
• if no limit is specified or the option is disabled, the server will manage the connection limits automatically.

PMM Agent

Similarly, you can now limit the number of connections that the PMM Agent opens to monitored databases for QAN, Advisors, and other systems.

Starting with this release, pmm-agent tracks all required resources (primarily connections), and opens no more than two connections per database instance simultaneously.

You can change this default value by setting a parameter or environment variable when starting the pmm-agennt.

For more information on configuring the PMM Agent and available parameters, see the PMM Agent help documentation by running pmm-agent --help.

Experimental PMM self-monitoring dashboard

We've added a new experimental PMM Health dashboard to provide detailed insights into the health and performance of PMM itself.

The dashboard reflects the PMM architecture and covers key components such as overall component status, node health, Query Analytics, PMM-managed, Grafana, VictoriaMetrics, ClickHouse, and PostgreSQL metrics.

This initial version is available in the Experimental folder after updating PMM and contains a starter set of key metrics to help identify potential issues and ensure optimal operation.

For more information about this new dashboard, see the Keeping an eye on the eye blog post.

Experimental MongoDB dashboards: Sharded Cluster and Replica Set

Along with the PMM Health Dashboard, we're also introducing experimental updates to two key MongoDB dashboards: the Cluster Summary and ReplicaSet dashboards. These new versions, accessible from the MongoDB section within PMM, have been redesigned to address feedback regarding readability and data density.

The design and navigation are simplified here, to focus on the essential parameters and metrics most relevant to MongoDB performance monitoring.

We encourage you to explore these experimental dashboards and provide feedback in the PMM forum to help us refine them.

Improvements

• PMM-3303 - We've introduced an experimental PMM Health dashboard in the Experimental folder, offering detailed insights into PMM's health and performance by covering key components such as node health, Query Analytics, Grafana, VictoriaMetrics, ClickHouse, and PostgreSQL metrics.

• PMM-13123 - Enhanced the Query Response Time Distribution graphs in the MySQL Query Response Time Details dashboard to provide more granular insights into query performance. Previously, the graphs did not include buckets for queries with response times less than 100 milliseconds, the range which many queries typically fall into. This limitation made it difficult to analyze the performance of sub-100ms queries, especially those in the sub-1ms range.

• PMM-13075 - Added support for Ubuntu 24.04 support.

• PMM-12896, PMM-12895, PMM-12971 - Added per-database metrics collection and control of parameters, enabling more granular data gathering without overusing connections.

• PMM-12994 - Added labels to the pg_replication_slot_slot_is_active and slot_current_wal_lsn metrics in the postgres_exporter to identify the replication type (logical or physical) and the plugin used for the slot.

• PMM-12753 - Added experimental versions of the MongoDB Cluster Summary and ReplicaSet dashboards with a streamlined design and simplified navigation, focusing on essential metrics for monitoring MongoDB performance.

• PMM-11583 - Added support for the innodb_redo_log_capacity variable introduced in MySQL 8.0, ensuring accurate and consistent data representation in the InnoDB Logging graphs.

• PMM-11278 - Improved the Query Analytics documentation to explain how QAN collects data. For more information, see the Query Analytics under the hood section in the [Query Analytics topic](https://docs.percona.com/p...

v2.41.2

Percona Monitoring and Management 2.41.2

Release date	March 20th, 2024
Installation	Installing Percona Monitoring and Management

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 highlights

Debian 12(Bookworm) pmm-client packages

Starting with PMM 2.41.2, we now offer pmm-client packages for the latest version of Debian. You can install these packages by following the instructions in our documentation.

Experimental dashboards

!!! warning "warning"
These experimental dashboards are subject to change. It is recommended to use these dashboards for testing purposes only.

As part of PMM 2.41.2, we have added the following experimental dashboards.

• Reworked Kubernetes dashboards
• Databases overview dashboard
• PostgreSQL Instance Summary dashboard
• PostgreSQL Checkpoints, Buffers and WAL Usage dashboard
• PostgreSQL Patroni dashboard

To access the experimental dashboards, go to the PMM home page and then navigate to Dashboards > Experimental from the side menu.

Alternatively, go to the PMM home page, navigate to Dashboards from the side menu, and enter the dashboard name in the Search for dashboards field.

Reworked Kubernetes dashboards

PMM 2.41.2 now features redesigned Kubernetes dashboards that offer improved clarity and usability.

• The redundant information has been removed from some of these dashboards.
• The Overview dashboard, which has now been renamed as Kubernetes Cluster Overview, has been reorganized and improved for better functionality.
• The DB Cluster dashboard has been renamed as Databases on Kubernetes and now displays dynamic information. Furthermore, it separates database/proxy details and shows resource limits.

These changes aim to improve user experience while adhering to PMM standards, particularly for managing multiple clusters.

Databases overview dashboard

The latest release introduces a new dashboard that offers a simplified overview of the databases being monitored by PMM. This dashboard aims to provide a centralized and unified place where the crucial parameters for database performance can be easily accessed.

If you're looking for more information on this dashboard, see the blog post.

PostgreSQL Instance Summary dashboard

The PostgreSQL Instance Summary dashboard is a newly designed feature that displays the critical PostgreSQL metrics. This dashboard aims to assist DBAs and developers in identifying PostgreSQL issues quickly.

PostgreSQL Checkpoints, Buffers and WAL Usage dashboard

In our continuous effort to enhance our dashboards, we have introduced this new experimental dashboard that provides more data about your PostgreSQL instances.

By leveraging this data, administrators can gain insights into their PostgreSQL servers and fine-tune their performance. Understanding and managing checkpoints, buffers, and WAL usage contribute to a well-performing and reliable PostgreSQL environment.

If you’re looking for in-depth insights into this dashboard, refer to our blog post.

PostgreSQL Patroni dashboard

Starting with PMM 2.41.2, we have included a new dashboard designed to monitor Patroni as an external service. For more information, see our documentation on external services.

This dashboard facilitates gathering more data for your PostgreSQL cluster inside PMM.

Read our blog post to learn more about this dashboard and how to add Patroni monitoring.

⚠️ Important
We would appreciate your feedback on these experimental dashboards to help us enhance it further.

Improvements

• PMM-10974 - Starting from PMM version 2.41.2, PMM has improved its stat tracking feature. In case pg_stat_monitor is not available, PMM will now use pg_stat_statements as a fallback option.

• PMM-12884 - In PMM dump, the Address field on the Send to Support screen now comes with the address and port pre-filled, making it easier to send logs to support.

• PMM-12887 - [Tech Preview] This new experimental dashboard has been added in PMM 2.41.2 for monitoring PostgreSQL checkpoints, buffers and WAL usage.

• PMM-12888 - [Tech Preview] This new experimental dashboard has been added in PMM 2.41.2 to monitor Patroni as an external service.

• PMM-12960 - [Tech Preview] The latest PMM release includes redesigned Kubernetes dashboards with improved clarity and usability.

• PMM-12981 - Starting with PMM 2.41.2, PMM can now collect wraparound metrics for PostgreSQL. By monitoring these wraparound-related metrics, PostgreSQL administrators can proactively manage wraparound risks and prevent potential data corruption and downtime.

• PMM-12894 - We have limited the number of connections used by postgres_exporter. Additionally, we have fixed an issue where connections are closed as soon as they are no longer needed, thereby preventing any hanging or idle connections.

• PMM-12897 - Previously, two heavy queries were running for each database in the PostgreSQL server at medium resolution, which impacted the performance. These queries have now been moved to low resolution to improve performance.

Fixed issues

• PMM-12806 - In previous versions, PMM Server used certain non-configurable Victoria Metrics settings with default values. With this release, we are updating this behavior to enable you to modify default values for Victoria Metrics settings using environment variables. Previously, environment variables were overlooked as Victoria metrics prioritized specific command line flags passed by PMM over environment variables.

• PMM-12348 - The ClickHouse engine was updated from the ordinary engine to the Atomic engine, which is the most robust engine, after upgrading PMM to version 2.41.0.

• PMM-12785 - Fixed an issue where VictoriaMetrics scrape configuration contained unsupported parameters.

• PMM-12805 - While monitoring MongoDB servers, the disk space was being consumed due to the CommandNotSupportedOnView message in the logs. This issue has now been resolved.

• PMM-12809 - Fixed several CVEs in PMM versions v2.40.1 and above.

• PMM-12852 - An internal server error was thrown while attempting to modify any setting in PMM. This issue has been resolved now.

• PMM-12986 - The PostgreSQL connections in use alert was triggering false positive notifications, but the issue has been resolved now.

• PMM-12948 - Fixed an issue where the wrong information was being displayed regarding the uptime of the PostgreSQL instance.

• PMM-12997 - The pmm-agent output was changed from stdout to stderr, which caused the automation to break. The issue has been resolved now.

v2.41.1

Percona Monitoring and Management 2.41.1

Release date	Feb 1st, 2024
Installation	Installing Percona Monitoring and Management

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 Highlights

Improved support for Arbiter nodes

We've made it easier to add and monitor MongoDB Arbiter nodes in PMM, as this no longer requires workarounds for cases where authorization is enabled on the MongoDB replica set. Additionally, Arbiter nodes are now displayed correctly on the dashboards:

New metric for sharded MongoDB insights

We've added a new metric to our MongoDB exporters: mongodb_shards_collection_chunks_count. This metric is available for sharded Mongo instances, offering insights into the distribution of collection chunks across different shards.

While this version is not currently integrated into any dashboard, you have the flexibility to incorporate it into your custom dashboards. For comprehensive instructions on managing dashboards, check out this video tutorial and the documentation.

New experimental MongoDB Instance Summary dashboard

This release also introduces a new MongoDB dashboard that offers a simplified view of the most critical MongoDB metrics. You can find the new MongoDB Instance Summary dashboard in the Experimental folder of your PMM installation. This dashboard is currently in Technical preview so we encourage you to evaluate its performance with your MongoDB instance and share your valuable feedback on our forum.

Improvements

• PMM-12390 - [Backup Management]: The Service name field on the Create Backup pages is now case-insensitive, allowing for more comprehensive and accurate results retrieval.
• PMM-12712 - MongoDB sharded cluster metrics now include a new metric to represent database and collection distribution across different shards. This helps gain insights into the overall balance of shards within MongoDB setups.
• PMM-12510 - Improved workflow for adding MongoDB Arbiter nodes to PMM, which also ensures that Arbiter nodes are now displayed correctly on the dashboards.
• PMM-12750 - [Dashboards]: Introduced an experimental MongoDB Instance Summary dashboard to provide a rapid overview of key MongoDB metrics.
• PMM-12866 - [Dashboards]: Minor UX improvements to the K8s experimental dashboard (Tech Preview).

Bugs Fixed

• PMM-12652 - Fixed issue where PMM failed to start after an upgrade, due to SELinux restrictions on accessing a PMM file created with root ownership on Podman. This fix applies to upgrades from PMM 2.41.0 to newer versions.
• PMM-9825 - [QAN]: PostgreSQL databases, monitored using the pg_stat_monitor extension v2.0+, were previously displayed with User IDs rather than actual User Names in the Service Name column on the Query Analytics (QAN) page. This issue is now fixed.
• PMM-12290 - [QAN]: Fixed bugs with SQL comments parsed in queries when they were not intentionally enabled for remotely added PostgreSQL and MySQL.
• PMM-12621 - [Dashboards]: Added support for the Anonymous mode to show all Service types on the main menu. This ensures users can access the dashboards, even when PMM is configured in Anonymous mode.
• PMM-12425 - [QAN]: The Absolute time range time picker on the Query Analytics (QAN) page no longer displays an error when using 'now' instead of a specific timestamp for filtering dashboard data.
• PMM-12473 - Fixed monitoring of external services when query string parameters are passed to --metrics-path.
• PMM-9407 - Fixed missing custom queries.yaml file for medium-resolution in Debian packages for PostgreSQL.
• PMM-12350 - Fixed issue of flood logs in mongod_exporter when connected to Mongos.
• PMM-12738 - Fixed issue that prevented PMM from running when using Helm with customer certificates.
• PMM-12781 - Corrected a permission error that was flooding PostgreSQL logs by ensuring proper execution permissions for the pg_ls_waldir function.

v2.41.0

Percona Monitoring and Management 2.41.0

Release date	Dec 12, 2023
Installation	Installing Percona Monitoring and Management

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

Release Highlights

Streamlined database problem reporting to Percona

To improve the gathering and sharing of PMM metrics and data, we’ve now integrated the pmm_dump client utility into PMM. Initially a standalone client for PMM Server, PMM Dump is now accessible in the PMM user interface.

This integration enables you to collect PMM data to share with our Support team.

To get started, in the main menu, go to Help > PMM Dump and select either to export a dataset locally or upload it to our SFTP servers using the credentials generated through your Percona Support ticket.

PostgreSQL monitoring: optimizing performance

PMM 2.41.0 introduces limit for Auto-discovery in PostgreSQL, a feature that dynamically discovers all databases in your PostgreSQL instance. Limiting Auto-discovery reduces connections and prevents high CPU and RAM usage caused by multiple databases, thus optimizing performance.

For details, see documentation.

PMM DBaaS functionality evolution into Percona Everest

We have decided to separate our DBaaS offering into an independent product. Consequently, we are discontinuing the DBaaS functionality in PMM and offering a migration path to Everest.

While the DBaaS functionality will remain available in PMM versions 2.x, all future updates and enhancements will be exclusively accessible through the Percona Everest interface.
For a more streamlined and robust database deployment experience, try Percona Everest.

Technical Preview of PMM in high availability (HA) mode

⚠️ Important
Disclaimer: This feature has been added in PMM 2.41.0 and is currently in Technical Preview. Early adopters are advised to use this feature for testing purposes only as it is subject to change.

Starting with this release, PMM can now be run in high availability mode with several PMM server applications and independent data sources.

Currently, PMM servers provide high availability, but users are responsible for maintaining the high availability of the data sources used by PMM.

These data sources are:

• ClickHouse: An open-source, fast analytical database.
• VictoriaMetrics: A scalable, long-term storage solution for time series data.
• PostgreSQL: A powerful open-source relational database management system used in this setup to store PMM data like inventory, settings, and other feature-related data.

If you're looking to dive deep into this feature, see our comprehensive documentation.

New Features

• PMM-12459 - The pmm_dump client utility previously available as a standalone client for PMM Server is now readily accessible within the PMM user interface.

Improvements

• PMM-11341 - PMM 2.41.0 introduces limit for Auto-discovery in PostgreSQL, a feature that dynamically discovers all databases in your PostgreSQL instance. Limiting Auto-discovery reduces connections and prevents high CPU and RAM usage caused by multiple databases, thus optimizing performance.
• PMM-12375 - Starting with PMM 2.41.0, each instance of a service gets a version attribute in the PMM Inventory UI.
• PMM-12422 - PMM 2.41.0 introduces a new flag called --expose-exporter. When you enable this flag any IP address, either from a local system or from anywhere on the internet, can access exporter endpoints. If the flag is not enabled, the exporter will be available only locally.
• PMM-12544 - Added deprecation notices to the PMM documentation DBaaS pages. For a more streamlined and robust database deployment experience, try Percona Everest.
• PMM-12549 - Added support for the latest MongoDB version. You can now use PMM to monitor MongoDB 7 databases.

Components upgrade

• PMM-12154 - Updated postgres_exporter to version 0.14.0. With this update, we have resolved several performance issues and eliminated the creation of multiple connections per database.
• PMM-12223 - Clickhouse has been updated to version 23.8.2.7, which optimizes memory and CPU usage to improve system performance.

Bugs Fixed

• PMM-4712 - We have addressed the issue where the pprof heap reports for postgres_exporter were missing.
• PMM-12626 - Due to the packages being built on an outdated Go version, there was a potential vulnerability. We have updated Go to the latest version to mitigate this risk.
• PMM-12414 - Fixed an issue with an unexpected behavior (502 response) when accessing the logs.zip endpoint. This was caused by the group_by parameter being included in the Alertmanager configuration. Additionally, we removed AlertManager-related files from logs.zip since we stopped using AlertManager.
• PMM-11714 - Registering a node with the Grafana Admin flag enabled but a non-admin role was failing. This issue has now been resolved.
• PMM-12660 - Prior to version 2.41.0 of PMM, the endpoint /v1/management/Agent/List could deliver database certificates to the PMM UI, allowing an authenticated admin user to view the output of TLS certificates. This posed a security issue since certificates should be consumed by the backend only. We have resolved this issue now.
• PMM-12630 - When users attempted to upgrade PMM versions lower than or equal to 2.37.1, the upgrade process got stuck in a loop and failed. The issue has been resolved now.
• PMM-12725 - Fixed the pagination for QAN.
• PMM-12658 - Corrected a typo in the MongoDB cluster summary dashboard.

v2.40.1

Percona Monitoring and Management 2.40.1

Release date:	Oct 20, 2023
Installation:	Installing Percona Monitoring and Management

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

Fixed issues

• PMM-12592 - Fixed an issue where the Library Panels for the PMM dashboard were not working after upgrade to PMM 2.40.0.
• PMM-12576 - After upgrading to PMM 2.40.0, changing the Admin user's password from the terminal was not functioning. The issue has been resolved now.
• PMM-12587 - After upgrading to PMM 2.40.0, some users may experience incorrect mappings between dashboards, folders, users, and groups. This can result in either a successful upgrade or a 500 internal server error. The issue has now been resolved.
• PMM-12590 CVE-2023-4911 is a vulnerability in the base OS that PMM is based on. It has been fixed in the base OS, and the fix is available in PMM.

How to upgrade to PMM 2.40.1

For instructions on upgrading to PMM 2.40.1 and mitigating issues from PMM 2.40.0, follow the steps below:

1. Copy the file from /srv/backup/grafana/grafana.db to /srv/grafana/grafana.db

   docker exec -t pmm-server cp /srv/backup/grafana/grafana.db /srv/grafana/grafana.db

2. Set permissions:

   chmod 640 /srv/grafana/grafana.db
   
   chown grafana:grafana /srv/grafana/grafana.db

3. Upgrade to 2.40.1 as usual.

v2.40.0

Percona Monitoring and Management 2.40.0

Release date:	Oct 05, 2023
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

Inventory improvements

Ability to update labels for existing services to PMM

Starting with PMM 2.40.0, editing labels for existing services is easier and much more efficient. You can edit a service label directly from the PMM UI without removing and re-adding it. For more information on editing labels, see documentation.

Furthermore, in our continued effort to enhance user experience, we have redesigned the following pages to make them more user-friendly and intuitive:

• Select service type page
• Add service page

Connecting Services and Nodes

Starting with PMM 2.40.0, you can click on the link in the Node Name column to view the node on which a specific service is running and analyze how node-level resource utilization impacts the performance of those services.

Before introducing this feature, locating the running services on a node was cumbersome. However, with this new feature, you can effortlessly access a list of services running on a specific node and identify the node name where the service is being utilized. Additionally, the filters implemented make navigation a lot simpler.

Furthermore, you can also see the service running on that specific node when you click on the link in the Services column.

Cluster view for Inventory

⚠️ Important
This feature is still in Technical Preview and is subject to change. We recommend that early adopters use this feature for evaluation purposes only.

Understanding the structure of your inventory is crucial. With the release of PMM 2.40.0, we've introduced an experimental feature that categorizes all your Services by Cluster, making it easier for you to understand your inventory. By using the Organize by Clusters toggle, you can view a group of services as a single cluster. PMM utilizes the cluster label to display services that belong to the same cluster.

For detailed information on this feature, see documentation.

MongoDB Backup Monitoring

With this release, we are shipping the first version of a the Backup failed alert template which notifies of any failed MongoDB backups. This uses a new, dedicated metric, pmm_managed_backups_artifacts, for checking the state of backup artifacts.

This new template is currently in Technical Preview and we are keen to get your feedback around this change before we move it to General Availability.

For information on working with this new template, see the Percona Alerting topic.

Components Upgrade

VictoriaMetrics has been upgraded v1.93.4.

New Features

• PMM-11963 - Starting with PMM 2.40.0, you can click on the link in the Node Name column to view the node on which a specific service is running.
• PMM-11148 - [Inventory]: We have redesigned the Select service type and Add service pages to make them more user-friendly and intuitive.
• PMM-11423 - [Inventory]: Starting with PMM 2.40.0, you can now edit service labels directly from the PMM UI without having to remove and re-add them.
• PMM-12378 - [Inventory]: We have introduced an experimental feature that categorizes all your Services by Cluster, making it easier for you to understand your inventory. By using the Organize by Clusters toggle, you can view a group of services as a single cluster.
• PMM-12384 - [Alerting]: Added a new built-in alert template, Backup failed which you can use to create alert rules that notify of failed MongoDB backups.
• PMM-9374 - [Technical Preview]: Starting with PMM 2.40.0, you can now use an external VictoriaMetrics database for monitoring in PMM. This provides multiple benefits, including scalability, resource isolation, reduced load on the PMM server, customization, etc.

Improvements

• PMM-4466 - Grafana now uses PostgreSQL instead of SQLite, resulting in improved performance, stability for user auth requests, data integrity, reliability, security, etc.
• PMM-12310 - Links from PMM to documentation may change, causing "broken links" in older PMM versions due to document structure changes. We have replaced all links with Short.io links specific to each document to address this. This way, we can maintain the PMM-to-doc links using a URL shortener. This ensures that the links remain accessible even if the document structure changes.
• PMM-12457 - We have added a new node_name property to the PMM agent down alert template in PMM. This allows users to easily identify the node where the failure occurred.
• PMM-12488 - VictoriaMetrics has been updated to v1.93.4.
• PMM-12500 - [Technical Preview]: For Percona Operator users, we have introduced a new dashboard for K8s monitoring with PMM 2.40.0.
• PMM-11770 - PMM now automatically sets the server domain value in grafana.ini to the public address specified in PMM’s Advanced Settings. This ensures that links generated by Grafana, such as links in alert emails, also carry that address.

Bugs Fixed

• PMM-10145 - When we installed an AMI image in AWS and added an Amazon RDS instance in the creating state, it caused errors. The issue has been resolved now.
• PMM-12173 - On adding several clients to PMM, unexpected and unauthorized errors caused PMM to stop responding. The issue has since been resolved now.
• PMM-12344 - An error was displayed on the Explain tab after selecting a PostgreSQL query. The issue has been resolved now.
• PMM-12361 - The command pmm-admin inventory returned GO errors. The issue has been reolved now.
• PMM-12382 - Fixed an issue where the upper-case custom labels were not being accepted.
• PMM-11371 - Usage of pmm-admin config subcommand shutdown pmm-agent. The issue has been resolved now.
• PMM-11603 - When running pmm-agent outside of systemd, adding an agent causes errors. The issue has been resolved now.
• PMM-11651 - When a user has both full access and limited access roles, only the limited role's metrics are displayed. The issue has been resolved now.
• PMM-12146 - Dead Tuples graph on PostgreSQL Vacuum Monitoring Dashboard displayed invalid percentage. The issue has been resolved now.
• PMM-12448 - Can't start backup if artifact with empty service_id exists.

Known issue

• PMM-12517 - If you have set custom dashboards as your Home dashboard in version 2.26.0, they may be lost after upgrading to version 2.40.0. To prevent this, we recommend that you back up your custom dashboard before upgrading and recover it after the upgrade.

v2.39.0

Percona Monitoring and Management 2.39.0

Release date:	Aug 14, 2023
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

MongoDB backups: UI-based restore on a new replica set cluster

Building on the recent MongoDB backup management enhancements, we have now added the option to restore backups on different clusters with the same configuration. This enables you to test restore data before deploying it on Dev environments.

Restoring on different clusters is not available for sharded clusters. This is a complicated process that still requires manual intervention. For more information, see Restoring from a sharded cluster

Query Analytics - Meta information

QAN is an important tool that can help filter data and identify problematic queries. However, it can be challenging to determine which services, nodes, and other labels are linked to these queries.

PMM 2.39.0 now includes a metadata table for QAN to address this issue. This table contains information such as Node name, Node name, Service name, Service type, and user name for each selected query. With this feature, you can easily identify the services, nodes, and labels associated with your identified queries.

To view the metadata table, navigate to the Main menu and click on Query Analytics (QAN). This will bring you to the Query Analytics page. Next, select the desired query and expand the Metadata tab. The metadata for that specific query will then be displayed.

Improvements

• PMM-6279 - [QAN]: PMM 2.39.0 now includes a metadata table for each query. This table contains information such as Node name, Node name, Service name, Service type, and user name for each selected query.
• PMM-10270 - [Backup Management]: Enhanced MongoDB Backup Management to support restoring to different replica set clusters with the same configuration.
• PMM-11999, PMM-12257 - [Advisors] - The Advisors page now contains a new Technology column that shows the database type for each advisor. This helps you distinguish between MongoDB, MySQL, and PostgreSQL advisors.
• PMM-11206 - [Alerting]: You can now easily add multiple Alert rule templates at once, whether through the API or UI. When added in bulk, each template will be displayed separately on the Alert rule templates page. This makes it quicker and more efficient to manage your alert rules.
• PMM-11637 - PMM UI now reflects the new PMM logo as per the new branding.
• PMM-12070 - We have updated the deprecated Boomtable plugin to the Grafana table plugin.
• PMM-12389 - The postgres_exporter now provides more comprehensive logs that display the specific namespace and error message for any issue.

Bugs Fixed

• PMM-12151 - [QAN]: The Explain plan was not displayed in a few scenarios. The issue has been resolved now.
• PMM-11658 - Fixed issue that caused the pmm-agent to crash on AMI and OVF distributions.
• PMM-11992 - Postgres databases with names other than Postgres could not be added. The issue has been resolved now.
• PMM-12263 - On the MongoDB Cluster Summary dashboard, the Replication Lag by Set graph showed the wrong value if rs was in the primary-secondary-arbiter (PSA) configuration. It calculated the arbiter's lag from the beginning of the UNIX time (currently >54 years instead of a few seconds). The issue has been resolved now.
• PMM-12280 - Fixed an issue where the Service Summary Panel on Home Dashboard used the incorrect units to display Available Memory.
• PMM-10665 - Fixed issue that caused QAN to show incorrect values when setting non-default values for performance schema. Make sure to restart pmm-agent after changing the settings for perfschema in MySQL.
• PMM-10391 - PMM did not work with external Clickhouse versions greater than 22.5.2. The issue has been resolved now.
• PMM-12231 - In the recent versions of PMM, users have encountered issues with installing, updating and removing plugins from PMM. For more information on this issue, see Troubleshooting Plugin issues.