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.

v2.38.1

Percona Monitoring and Management 2.38.1

Release date:	July 13, 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 issue

PMM-12293 - The upgrade to Grafana 9.2.20 in PMM 2.38 fixed critical security CVE-2023-3128 by changing the authentication mechanism to rely solely on the user's unique ID provided by the identity provider.

This change caused an authentication issue for second and subsequent connections to PMM using a Percona Account. With this PMM update, we are fixing this authentication issue to ensure that users can log back into PMM after an initial connection. Previously, this would fail with a "User already exists" error.

If you are using a third-party authentication provider and continue to see this issue, pass the GF_AUTH_OAUTH_ALLOW_INSECURE_EMAIL_LOOKUP=1 environment variable to the PMM container.

Alternatively, set the oauth_allow_insecure_email_lookup config key in the auth section of the grafana.ini file. Keep in mind that any changes you make to this file are lost when upgrading PMM, so make sure to manually update this file after each upgrade.

v2.38.0

Percona Monitoring and Management 2.38.0

Release date:	Jul 3, 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

Important security updates

Oracle Linux 9 as new base OS for PMM

As security is paramount to us, PMM 2.38.0 adds a solid and modernized enterprise-grade foundation to PMM. This release migrates our base operating system on which we build our PMM image from CentOS 7 to Oracle Linux 9.
Thus, starting with PMM 2.38.0, PMM is publicly available on Oracle Linux 9.

This transition brings many benefits:

• a large number of CVEs automatically fixed
• improved upstream response time to security-related issues
• better compatibility with new technologies
• modern libraries for our team to build on

Since not all users will be able to seamlessly make the move, we will be rolling this out in phases:

Automated migration paths

The following users will be able to take advantage of this immediately:

• New installations of PMM:

  • Docker containers from our Docker hub: percona/pmm-server:2
  • OVF: Download directly from our website
  • AMI: Loaded from AWS Marketplace

• Docker/Podman users who do full container replacement upgrades to newer versions of PMM.
  Your existing docker pull or docker run commands will use the new image.

Manual upgrade options

If you are upgrading through the UI’s Upgrade Now button, you'll have to wait a little longer for an automated migration path. This includes:

• Docker users that use UI upgrade
• AMI users
• OVF users

If you want to upgrade manually in the meantime, check out the instructions in the PMM is getting a modernized enterprise-grade foundation blog post.

Grafana upgrade

PMM now uses Grafana to 9.2.20, which fixes some critical vulnerabilities. For more information, see Grafana's release blog.

Exporters

Updated the mysqld_exporter, node_exporter, postgres_exporter, and mongo_exporter to fix the CVEs.

ClickHouse plugin

We have migrated from the Altinity Clickhouse datasource to the Grafana Clickhouse datasource due to the vulnerabilities discovered.

Due to this migration, we have also updated our experimental Environment Overview Dashboard.

⚠️ Important
Though we have removed the datasource from PMM, we are still reusing the same name (ClickHouse) to keep the changes minimal. Thus, if you are using the old datasource in your dashboards, ensure that you upgrade the underlying queries that will pull the data from the new datasource.

Example

The following example shows the difference in the query before and after migration.

Before migration:

// Altinity ClickHouse datasource
SELECT $timeSeries as t, 
    sum(m_query_time_sum)/sum(m_query_time_cnt) as QLatency,
    environment
FROM $table
WHERE $timeFilter and environment != ''
GROUP BY t,environment
ORDER BY t

After migration:

// Grafana ClickHouse datasource
SELECT period_start as t,
    sum(m_query_time_sum)/sum(m_query_time_cnt) as QLatency,
    environment
FROM pmm."metrics" 
WHERE $__timeFilter(period_start) AND environment != ''
GROUP BY t, environment
ORDER BY t

Altinity data sources used macros like $timeSeries, $timeFilter, and $table, which are no longer present in the Grafana datasource. As a result, the query needs to be rewritten to use the new macros instead of the old ones.
You will notice that in the example above, the macro $timeFilter has changed to $__timeFilter, and now it requires a parameter, which should be a column of type datetime.

Depending on which macros you have used, your migration effort will vary. However, we recommend checking the plugin documentation to apply the new syntax correctly, including macros and template variables.

Improved nodes view on the Inventory page

In our continuing endeavor to enhance user experience, we further improved the Inventory page by improving the Nodes tab. With this change, you can get more context on your inventory objects, such as nodes, and more actionable information for exploring and resolving possible issues.

Here is the change as part of PMM 2.38.0:

• Check the number of agents running on any particular node. When you click on any node, the UI navigates to the view of agents, which is filtered to display only agents related to that specific node.

  To see the details of the agents running:

  On the Nodes tab, under the Monitoring column, click OK or Failed, depending on the status of the node that you have selected. A page that provides the user with crucial information regarding the total number of agents deployed on that node is displayed.
  

• View comprehensive information about each agent, including key attributes such as node type, IP address, and associated services. This gives you a complete overview of the nodes at a glance.

  

• Check the health status of the agents to see if they are running or have failed.

Backup enhancements

Better folder management for enhanced PBM compatibility

We’ve added a new Folder field to the Create Backup pages. Use this to set a specific target directory within the selected local or S3-compatible location for the backup.

Organizing backups in folders makes grouping PBM backups for clusters easier, and it improves PMM-PBM (Percona Backup for MongoDB) integration workflows.

The Folder field is automatically populated with the value of the cluster label. You can change this default folder from PMM’s Advanced Settings, but make sure you understand how your custom folder will impact PBM integration workflows.

Sharded cluster MongoDB backup support

This release introduces support for working with backups for sharded clusters. PMM handles the backup process end-to-end, but restoring such artifacts is currently possible only via the CLI, using Percona Backup for MongoDB.

For information on restoring sharded backups, check the PBM documentation.

SQL comments support in QAN

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

You can now collect labels from the comments placed in SQL queries. You can tag the query by key value in the query comment. This helps in query management and optimization. This feature is currently supported for MySQL and PostgreSQL.

For example:

SELECT * /* cluster=’east’ */ FROM city;   

You can enable this feature as follows:

• CLI - Pass the parameter comments-parsing

• UI - It is enabled by default. To disable, uncheck the Disable comments parsing checkbox in the Additional Options section. This is supported for PostgreSQL and MySQL.

  

New PMM Agent Down alert template

We've added a new default alert template to Percona Alerting.

The new PMM Agent down alert template monitors your Node status to notify if the Agent is down. Before using this template:

• ensure the PMM Agent is healthy and present on the Database Node.
• check that PMM Client is on version 2.38 version or later.

Grafana upgrade

PMM now uses Grafana v9.2.20, which includes fixes for some critical vulnerabilities. For more information, see Grafana's release blog.

New Features

• PMM-2852 - [QAN]: Starting with PMM 2.38.0, MySQL and PostgreSQL supports collection of labels from the comments placed in the SQL queries.
• PMM-11961 - [Inventory]: Starting with PMM 2.38.0, we have enhanced the Inventory page by improving the Nodes tab. With this change, you can get more context on your inventory objects, such as node, and more actionable information for exploring and resolving possible issues.
• PMM-11962 - ...

v2.37.1

Percona Monitoring and Management 2.37.1

Release date:	Jun 5, 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.

⚠️ Important
We recommend using the latest version of PMM. This ensures that you have access to the latest PMM features and that your environment runs on the latest version of the underlying components, such as VictoriaMetrics, with all the bug fixes in place.

Release Highlights

We have identified and fixed CVE-2023-34409 in PMM 2.37.1:

PMM-12182: PMM authentication bypass vulnerability

Workaround

If you are unable to update PMM you can resolve this issue as follows:

1. Make changes to the NGINX configuration on the running PMM instance. To do so, create a Bash script with the code from this script on GitHub.

2. Apply the code using this docker command on a server running the PMM Docker container (as root or using sudo):

   docker exec -it pmm-server bash -c 'curl -fsSL https://raw.githubusercontent.com/percona/pmm/main/scripts/authfix.sh  | /bin/bash '

3. If you are running PMM via a virtual appliance (OVF or AMI), use SSH to shell into the PMM server and run this command:

   curl -fsSL https://raw.githubusercontent.com/percona/pmm/main/scripts/authfix.sh  | /bin/bash

For more details see, blogpost.

v2.37.0

Percona Monitoring and Management 2.37.0

Release date:	May 02, 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

Improved Inventory view

This release of PMM starts the series of enhancements that will improve the way you work with Services and Nodes in PMM.
With this first set of changes, we’re revamping the Inventory page to give you more context on your inventory objects, and more actionable information for exploring and fixing possible issues.

Here are all the specific changes:

• Improved design of the Inventory page for a clearer presentation of all the objects registered by PMM.
• Services now show their database status, which is based on the monitoring metrics. This enables you to quickly check the status of the databases when you are working with the inventory.
• New Monitoring column showing the live status for the monitoring Agents assigned to a Service. This enables you to quickly spot any possible issues with the Agents.
• Quick access to the Service Summary Dashboard and to QueryAnalytics results so that you can easily explore important related information.
• New Details section grouping together all the relevant parameters and labels for a Service. To keep things clean, this section is collapsed by default, so that you can view extra information only when you need it.

Here's what's coming:

Building up on these changes, subsequent releases will further improve PMM Inventory with:

• More useful features to filter and better connect Services and Nodes.
• Services organized in clusters so that you can capture the bigger picture, instead of working at of individual Service-level.

New Experimental Dashboards for Kubernetes Monitoring

⚠️ Important
These experimental dashboards are subject to change. It is recommended to use these dashboards for testing purposes only.

We are pleased to announce the release of PMM 2.37, which introduces three new experimental dashboards:

• Kubernetes Cluster Summary
• Kubernetes Pods Status
• Kubernetes Volumes

These dashboards are designed to provide valuable insights into the status and performance of your Kubernetes cluster, pods, and volumes, helping you to identify and troubleshoot issues quickly and easily.

We welcome your feedback as we continue to enhance PMM with these new dashboards.

Experimental Kubernetes Cluster Summary Dashboard

Kubernetes Cluster Summary provides a comprehensive overview of your Kubernetes cluster, including:

• Components
• Node
• Pod
• PVC status
• CPU
• Memory overview, and more.

This dashboard displays all workloads running in the cluster, enabling you to take action and optimize its performance.

Experimental Kubernetes Pods Status Dashboard

Kubernetes Pods Status dashboard provides detailed information about the state and performance of your pods, including CPU, Memory, and Network metrics.

This dashboard can help you quickly pinpoint any issues affecting your pods and ensure they continue to operate smoothly.

Experimental Kubernetes Volume Dashboard

Kubernetes Volumes dashboard provides insights into your Kubernetes volumes, including capacity and usage, in real time. With this dashboard, you can easily monitor the performance and usage of your volumes and take proactive measures to ensure their performance.

Refer to the documentation to learn more about these new experimental dashboards and how to use them.

Here are the steps to create a new folder and move all experimental dashboards to the new folder for quick access and internal use:

📝 Note
You should have at least an Editor role to create a new folder and move all experimental dashboards.

1. Navigate to the Main menu and hover on the {{icon.dashboards}} Dashboards icon.
2. Click New folder.
3. Provide a name for your folder, and then select Create.
4. Navigate to {{icon.dashboards}} Dashboards from the Main menu and click Browse.
5. Select the dashboard that you want to move and click Move.
6. On the Choose Dashboard dialogue box, from the dropdown under Folder option, choose the folder where you want to move the dashboard.
7. To apply your changes, select Save Dashboard.

Components upgrade

VictoriaMetrics has been upgraded to version [1.89.1].

New Features

• PMM-10913 - Starting with PMM 2.37.0, you can use an external PostgreSQL server as data storage for PMM. Thus, even if PMM fails, your data will be stored in an external source, reducing the risk associated with data loss. Furthermore, clustered PostgreSQL instances also enhance performance.

• PMM-11281 - We have written a query for the postgres exporter to deal with lock conflicts in databases that block several transactions, thus impacting performance. With this query, you can find the PID of the blocking session and how many sessions it blocked. The proactive approach enables customers to address non-responsive databases quickly by understanding the underlying causes.

• PMM-11384 and PMM-11834 - PMM 2.37.0 now supports PSMDB operator versions 1.13 and 1.14.

• PMM-11438 - Starting with PMM 2.37.0, PMM administrators can disable the internal PostgreSQL server, which helps to fine-tune the server.

• PMM-11439 - Starting with PMM 2.37.0, a PMM administrator can now view metrics from an external PostgreSQL server.

Improvements

• PMM-11412 - We have enhanced our dashboards to be more user-oriented, displaying the DB cluster's status along with its components, such as metrics of stateful, pods, and so on. Also, you can apply filters based on DB name or DB type.
• PMM-11832 - When hovering over the Backup option on the main menu, PMM now displays the subcategories for easier navigation.
• PMM-11522 - With the newly added support for Clickhouse as a datasource for Advisors, Advisors can now use data produced by Query Analytics (QAN) to run checks on databases.
• PMM-11544 - Improved functionality for EXPLAIN query in QAN.
• PMM-11926 - Updated the format of the Upgrade to a Premium plan URL on the Advisor Insights page.
• PMM-11078 - Following the replacement of Integrated Alerting with Percona Alerting in PMM 2.311, we have now phased out all the APIs related to this deprecated feature.

Bugs Fixed

• PMM-8690 - Fixed an issue where the Replica set lag displayed incorrect values on the MongoDB ReplSet Summary dashboard for an ARBITER node.
• PMM-9775 - QAN: PMM failed to display the set timezone for QAN despite it being set to UTC.
• PMM-10687 - DBaaS: Fixed an issue where DB cluster creation failed when using an unreleased version of pmm-server.
• PMM-11121 - DBaaS: Fixed an issue where the list of DB clusters did not load if one of the K8s clusters was unresponsive.
• PMM-11226 - Fixed an issue where different operator versions and names were displayed for each K8s cluster.
• PMM-11313 - Rows Fetched/Read and Users by Rows Read dashboards are not working in the MySQL User Details dashboard
• PMM-11555 - For thousands of client connections for ProxySQL, the graph for Active Frontend connections did not render due to sluggish performance. Furthermore, this could affect the rendering and usage of the ProxySQL Instance summary dashboard. The issue has been resolved now.
• PMM-11829 - PMM Agent does not work with PG 12 and PGSM 2.0. This issue has been resolved now.
• PMM-11844 - Fixed an issue where a user failed to add PSMDB with pmm-admin using native LDAP authentication and TLS.
• PMM-11862 - Fixed inconsistent naming of the Advisors feature across PMM UI.
• PMM-11875 - Fixed an issue where the users could not select and compare multiple nodes on the Summary dashboard.
• PMM-11904 - Index Size and Concurrent Inserts panels were broken on the Insight / VictoriaMetrics dashboard after updating to version 1.89.1.
• PMM-10795 - Node summary was not visible under MongoDB ReplSet Summary when the node name contained a dot (.) in the name.
• PMM-11465 - Fixed problem with empty output for EXPLAIN in ...

v2.36.0

Percona Monitoring and Management 2.36.0

Release date:	Mar 23, 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

pg_stat_monitor 2.0 support in QAN

We are excited to announce PMM 2.36 now supports pg_stat_monitor 2.0 (PGSM 2.0) in QAN, a powerful PostgreSQL query performance monitoring tool. By downloading this update, you will have access to the latest improvements and fixes covered by PGSM2, including:

• Improved internal architecture that results in fewer lock acquisitions and increases performance by approximately 20%.
• Support for PostgreSQL 15
• Enhanced consistency with pg_stat_statements so that the pg_stat_monitor view has identical column names, columns, and data types as pg_stat_statements for every major version of PostgreSQL from versions 11 to 15.
• A bucket status indication (done vs. current) eliminates the need for the tool to evaluate bucket status and facilitates accurate data display.
• The generation of a unique ID for a query makes it easier to monitor query planning, execution, and performance regardless of version, database, user, or schema.

For more information on the enhancements in PGSM2, refer to the full list.

⚠️ Important
PostgreSQL versions 11 and 12, along with PGSM 2.0, will be supported in PMM 2.37.0.

Revamped Advisors page

We’ve improved the structure of the Advisors page to group Advisors by categories and clearly show the Advisors available for your current subscription.

With this change, we have renamed all the tabs on the page, and added an option to easily integrate with Percona Platform for extra Advisors for free:

PostgreSQL Advisors executed against more databases (DBs)

To give you additional insights on your PostgreSQL DBs, PostgreSQL Advisors now try to perform checks on all the databases accessible with the credentials used during pmm-client setup.
In most cases, these are the databases available for the PMM database account user. For more information, see the Create a database account for PMM topic in the PMM online Help."

Backup Management enabled by default

Since the PMM 2.32 release, we have continuously improved the Backup Management functionality in terms of backup locations, restore options and user experience.

As a mature and generally useful feature, this option is now enabled by default for easier access to your backups and restore artifacts.

📝 Note
- Upgrading to PMM will automatically enable this feature for existing PMM instances. You can disable it at any time from your PMM dashboard on the Advanced Settings page or using the Docker environment variable DISABLE_BACKUP_MANAGEMENT=1.
- While we have GA'ed Backup Management for MongoDB since PMM 2.32, Backup Management for MySQL still in technical preview, and, therefore, subject to change. For more information, see the Percona Release Lifecycle.

Components upgrade

Grafana has been upgraded to version 9.2.13.

New Features

• PMM-9474 - PostgreSQL Advisors are now executed against all the available databases (DBs), not only the one connected to PMM
• PMM-11363 - Starting with PMM 2.36.0, you no longer need to unassign a role before deleting it. If you try to delete a role assigned to a user, you will see a dropdown with replacement roles. As a result, the selected role will be assigned to the user.

Improvements

• PMM-11640 - [Backup Management]: The Backup Management feature is now enabled by deault forf easier access to your backups and restore artifacts.

• PMM-11182 - [Platform integration]: Renamed the Disconnect button on the confirmation message that pop-ups when you are terminating Percona Platform connections as an Administrator. The button is now called Force disconnect to better differentiate between situations where you are disconnecting using a Percona Platform Account.

  Force-disconnecting only clears the connection in PMM without automatically removing the disconnected servers from Percona Platform. We recommend that you always disconnect while logged in with your Percona Account. Otherwise, make sure to manually remove the force-disconnected servers from your list of PMM instances in Percona Platform.

• PMM-11381 - Starting with PMM 2.36.0, you can scrape Kubelet metrics with DBaaS or VictoriaMetrics operator. Using Kubelet metrics, you can gather volume-related information.

• PMM-11566 - You now have Admin Access to PMM Demo instances so that you can experiment with all the features of PMM.

• PMM-11699 - Improved documentation and descriptions for Advisor checks.

• PMM-10974 - Usage of pg_stat_monitor by default.

Bugs Fixed

• PMM-11291 - [DBaaS]: There was a difference in the shape and color of the DB Cluster Status box compared to the Kubernetes Cluster status box. The issue has been resolved now.
• PMM-11296 - [DBaaS]: Fixed an issue where the DB Cluster creation page did not load when DBaaS was disabled.
• PMM-11358 - [DBaaS]: Connection to the DB cluster displayed a loader when the DB cluster was suspended/paused. The issue has been resolved now.
• PMM-11613 - [DBaaS]: Backups could not be created when uppercase letters were used in the storage name. The issue has been resolved now.
• PMM-11568 - [DBaaS]: Disabled the selection of MySQL versions less than 8.0.27.
• PMM-11766 - [DBaaS]: The status of an unavailable cluster was displayed as Active. When this cluster was unregistered, an error was thrown. The issue has been resolved now.
• PMM-11428 - [DBaaS]: Fixed an issue where editing DB clusters was broken.
• PMM-10254 - [Dashboards]: On the MySQL/Mongo dashboards, the Memory Available graph showed incorrect values. The issue has been resolved now.
• PMM-11209 - [Backup Management]: Improved error handling for partially successful restores. Restore jobs that finished successfully on some nodes and failed on others are no longer locked in a Pending state. Instead, PMM now shows a PartlyDone error and populates the logs with specific details on the restore status for the replica set and nodesup restores.
• PMM-10606 - Fixed an issue for the incorrect link for node name on the mysql instance summary dashboard.
• PMM-11001 - Fixed an error that occurred in certain scenarios when expanding alert rules nested in folders.
• PMM-11004 - Fixed issue that ignored the database name provided when adding PG server to PMM.
• PMM-11408 - Navigation from the New Home dashboard panel to certain dashboards is broken. The issue has been resolved now.
• PMM-11421 - Improved error message that is displayed when trying to connect PMM to Percona Platform over HTTP Proxies: "PMM Platform connection does not support proxy".
• PMM-11526 - On the Summary dashboard, the error message exit status 1 has been replaced with a more meaningful message.
• PMM-11588 - Fixed an issue where the database instance count on the OS Overview dashboard was incorrect.
• PMM-11636 - The Grafana Admin page crashed when filtering users. The issue has been resolved now.
• PMM-11654 - There was no data displayed on the PXC Galera replication latency dashboard. The issue has been resolved now.
• PMM-11664 - Fixed an issue for the environment filter missing from the OS dashboards.
• PMM-11717 - Mysql exporter agent stopped working after upgrading the server to PMM 2.36.0. The issue has been resolved now.

v2.35.0

Percona Monitoring and Management 2.35.0

Release date:	Feb 23, 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

Access Control: Limit access to metrics

⚠️ Important/Caution
Disclaimer: PMM Access Control is still in Technical Preview and is subject to change. We recommend that early adopters use this feature for testing purposes only.

We are pleased to announce that PMM 2.35.0 marks the first step towards introducing PMM Access Control. Label-based access control in PMM allows you to manage who has access to metrics based on labels.

By creating roles, you can specify which data can be queried based on specific label criteria, for instance, allowing the QA team to view data related to test environments. Using this feature, you can associate multiple labels with a role, ensuring only data from series that match your defined labels is returned.

This feature provides a standardized method for granting, changing, and revoking access to metrics, giving you a powerful and flexible way to manage access to metrics and ensure secure access to the information you need. For more information, see documentation.

GA: Deployment of PMM in Kubernetes with Helm Chart

We are happy to announce the General Availability of PMM deployment in Kubernetes with the Helm chart. PMM deployment via Helm chart in Kubernetes has been available as Tech Preview since PMM v2.29, but now we're delighted to offer it to users as a fully supported feature. For more information, see documentation.

DBaaS: Add a backup schedule while creating DB clusters

Starting with PMM 2.35.0, you can add a backup schedule while creating DB clusters in DBaaS. This feature is a fusion of backup management and DBaaS in PMM. Currently, DBaaS only supports scheduled backups, which can only be enabled when a database cluster is created.

DBaaS does not support on-demand backups.

DBaaS: Restore cluster from backup stored on S3

You can now create a DBaaS cluster from a backup stored on S3. You can use backups taken from existing cluster and use them to spin-up a new database cluster from this backup. Attempts to use it to restore a previous version of the cluster will result in downtime since the system will treat it as a creation of a new cluster.
`
DBaaS does not support on-demand restore.

More pre-run checks for MongoDB backups

With this release, PMM runs additional verifications to ensure infrastructure compliance and prevent backup execution errors:

Tool compatibility check

Before initiating backups for MongoDB, PMM now examines the current MongoDB node to ensure that the connected PMM Agents have the tools to execute and finalize the backup.

If the requirements are not met, PMM reports what tools or tool versions are missing, similarly to the existing prerequisites check for MySQL backups.

Overlapping jobs check

To avoid conflicting jobs, PMM proactively disables the creation of Point-in-time Recovery (PITR), or snapshot backups, when other backups are scheduled for running.

Similarly, creating PITR backups for different services of the same cluster is now automatically restricted.

Cluster membership check

To avoid execution errors, PMM no longer allows scheduling backups on MongoDB Services that are not managed as a cluster.

You can check which of your current Services are not members of a cluster on the PMM Inventory > Services page. Services that do not specify a cluster name in the Other Details column should be removed and re-added using the following set of commands:

pmm-admin add mongodb
username=pmm_mongodb --password=password 
query-source=profiler --cluster=mycluster

Backup restore logs accessible from PMM

With this release, we are adding the option to view the logs for restores from a MongoDB database backup.
This complements the existing option to view the logs for the backup process and makes it easier to gather data for compliance, auditing, and troubleshooting purposes.

Instead of having to look through PBM log files, you can now access the Log option in PMM, which is now automatically displayed next to each MongoDB backup restore entry on the Backup > Restores page.

Components Upgrade

MongoDB exporter has been upgraded to 0.37.0.

New Features

• PMM-10325 - Starting with PMM 2.35.0, for enhanced security, you can change the admin password even after pmm-agent is registered on the PMM Server.

• PMM-10550 - [Backup Management]: PMM now automatically displays a Logs option next to each MongoDB backup restore entry on the Backup > Restores page.

• PMM-11302 - [DBaaS]: Starting with PMM 2.35.0, you can add a backup schedule while creating DB clusters in DBaaS. You can also restore the cluster from backup stored on S3.

• PMM-10962 - Starting with PMM 2.35.0, we have introduced Access Control. Roles are a vital part of Access Control that provide the users with access to specified metrics. You can create, edit, and delete user roles. The roles can be assigned to the users with the Configuration > Users tab. For more information, see documentation.

Improvements

• PMM-10471 - [Backup Management]: PMM now automatically checks the current MongoDB node to ensure that the connected PMM Agents have the tools to execute and finalize the backup.

• PMM-11113 - Enhanced user experience for the Percona Platform page under Configuration > Settings. The new version of this page highlights the advantages of connecting your PMM instance to Percona Platform and makes it easier to generate and use a connection token.

Bugs Fixed

• PMM-9446 - Fixed an issue with the MySQL/MySQL Details dashboard, where the users' names were overlapping.

• PMM-10016 - [Advisors]: The list of checks in the Failed Checks table would randomly rearrange after clicking on any of the checks in the list. This issue is now resolved.

• PMM-10109 - [DBaaS]: Fixed an issue that prevented the creation of DB clusters when performing a List query.

• PMM-11290 - [DBaaS] Fixed an issue where the Advance option in Edit DB cluster disabled the Edit/Save option.

• PMM-11474 - [DBaaS]: An internal server error was thrown on the UI while upgrading PMM to 2.34.0, and DB clusters were not visible in the UI. The issue has been resolved now.

• PMM-11062 - Fixed an issue where the Check update button was not visible.

• PMM-11116 - Despite PMM-gent being connected, the status of all other agents was Unknown. The issue has been resolved now.

• PMM-11154 - Fixed an issue where all agents except pmm-agent display NULL values in version and runs_on_node_id fields in the agents table of internal PostgreSQL database.

• PMM-11186 - Check that service is a member of a cluster before MongoDB backup/restore

• PMM-11274 - "Postgresql exporter error" was thrown for all nodes after upgrading from 2.29.0 to 2.33.0. The issue has been resolved now.

• PMM-11298 - While monitoring the performance of VictoriaMetrics with PMM 2.33.0, the CPU usage shown on Node Summary or VictoriaMetrics dashboard overview panel did not match the value shown on the system Level Metrics panel. The issue has been resolved now.

• PMM-11357 - [Percona Alerting]: Fixed an issue where the name of an alert rule was not inherited correctly from the alert template.

• PMM-11399 - [Percona Alerting]: The pop-up message that confirmed saving an alert rule would not display the name of the rule correctly. This issue is now resolved.

• PMM-11517 - [Backup Management]: Fixed a PBM synchronization issue that made PMM unable to restore local physical backups after the first attempt.

Coming Soon

Access Management

The following features/use cases will be covered as part of the various stages of PMM Access Management:

Role-based access control (RBAC), including access limitations to the features like Alerting and Backup with read-edit-delete permissions.

PMM High Availability

PMM High Availability (HA) fe...

v2.34.0

Percona Monitoring and Management 2.34.0

Release date:	January 30, 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

Various UX enhancements to Backup Management

With this release, we are updating the Backup and Restore functionality with key usability enhancements, including:

• Filtering on services at backup creation time. This makes it considerably easier to find the right service for a backup when working with multiple servers.
• Automatic redirection to the Restores page after initiating a restore. From here you can immediately monitor the restore process, and see the restore history for your PMM instance.
• Added information about the type of storage for the backup artifacts on the All backups page. This helps you get a more comprehensive overview of your current backups.
• Design and usability improvements on the Create Backup and All Backups page to increase consistency with other PMM UI controls.

DBaaS migration

Starting with PMM 2.34.0, PMM installs and manages operators using Operator Lifecycle Manager (OLM) and database clusters using dbaas-operator. Nonetheless, these changes are backward incompatible, and you must perform these additional steps:

1. Force unregister the Kubernetes cluster from PMM (select Ignore errors checkbox) and register it back. PMM will install OLM and dbaas-catalog to manage the lifecycle of PXC, PSMDB, and DBaaS operators.
2. Create a database cluster for each cluster you have created in PMM. You can use the script to do it automatically during the maintenance window. Migration scripts use the default configuration to connect to Kubernetes clusters and run migrations against them.

New components

We have a newly added component, VMProxy starting with PMM 2.34.0. VMProxy is a stateless reverse proxy that proxies requests to VictoriaMetrics and optionally adds extra_filters query based on the provided configuration.

New Features

PMM-11031 - To enhance the DBaaS experience, the UI has been extended to include the following:

• Network and Security - DBaaS users can set a source range from which they can connect to their DB clusters with the Expose field. You can modify the exposure level using the Source Range field. Additionally, the Source Range field allows you to choose the network from which you can connect.
• Configuring the database engine - Copy-paste the config string into the Configuration text box to configure the database engine.
• Configuring storage classes - You can choose from the available classes.

Improvements

• PMM-11024 - [DBaaS]: Move from dbaas-controller to dbaas-operator
• PMM-10873 - [DBaaS]: Create DB Cluster: We have modified the UI to include a separate window rather than a popup so that creating a DB cluster is easier.
• PMM-11132 - [DBaaS]: During K8s cluster registration, a new state called Provisioning is added. Provisioning is the default state, and once that is completed, the state will change to Active.
• PMM-11134 - [DBaaS]: Edit DB Cluster: We have modified the UI to include a separate window rather than a popup so that editing a DB cluster is easier.
• PMM-9262 - [Backups]: After starting a backup restore from the All Backups page, PMM now automatically redirects you to the Restores tab, where you can check the status of your new restore.
• PMM-11086 - [Backups]: Improved design for the On Demand and Schedule Backup cards on the Create Backup page. In addition, the Created column on the Restores tab has been replaced with Started at and Ended columns to provide more insight into the restore process.
• PMM-10924 - [Backups]: The Location column on the All Backups page has been enhanced to include information about the storage type used for the backup: Local or S3-compatible.
• PMM-11171 - [Backups]: The Service name field on the Create Backup page is now searchable. This makes it easier to find the right service for a new backup when working with multiple servers. Just paste the name of the server you're looking for, or start typing to see the list of matching servers.
• PMM-9079 - [Backups]: Added Target Service column under Backup > Restores to show the service to which a backup was restored.
• PMM-10773 - [Alerting]: Added option to unsilence alerts from the Actions menu under Alerting > Fired Alerts.
• PMM-11230 - [Alerting]: The Fired alerts page under Alerting now auto-refreshes more frequently to ensure that any new alerts are displayed in real-time.
• PMM-11255 - [Alerting]: PMM no longer transfers the name of the current alert rule when switching from Percona templated alert to Grafana managed alert.
• PMM-11090 - The Logs feature has been moved from the dbaas-controller to PMM, providing users with the ability to see the events for each pod and the logs for every container properly populated within PMM.
• PMM-11179 - Starting with PMM 2.34.0, we support push metrics mode while updating labels.
• PMM-11189 - Starting With PMM 2.34.0, we have implemented vmproxy integration and frontend API changes.
• PMM-10705 - [DBaaS]: As of PMM 2.34.0, Operator Lifecycle Management (OLM) is used for handling the installation and updating of operators for PMM in an effective, automated, and scalable manner.
• PMM-11069 - [Backups]: PMM no longer allows creating backup tasks with a name that already exists. After upgrading to PMM 2.34, any backup tasks with duplicate names are automatically renamed to apply the new naming constraints.

Bugs Fixed

• PMM-7350 - [DBaaS]: Fixed an issue where DB Cluster did not restart all PXC servers and proxy SQL servers on restarting.
• PMM-11333 - [DBaaS]: Fixed an issue where the API key was missing on K8s cluster registration after moving to Operator Lifecycle Management (OLM).
• PMM-9505 - [DBaaS]: The options to update, restart, and view logs were enabled for paused clusters. This issue has now been resolved by disabling these options.
• PMM-11221 - [DBaaS]: Fixed an issue where the page did not load when DBaaS was disabled.
• PMM-7958 - During Postgres monitoring, databases were not getting deleted. This issue has been resolved now.
• PMM-9977 - [Backups]: After deleting an expanded row from the Backup > All Backups page, PMM would automatically expand the next row in the table. This issue is now fixed and PMM refreshes the list of backups artifacts without automatically expanding any rows.
• PMM-10942 - [Backups] - The scheduler for PITR backups now use clearer text labels to better define the Start time and the Frequency for the backups being created.
• PMM-10853 - [Alerting]: Removed Save button from the Create alert rule page as this was duplicating the functionality of the Save and exit button.
• PMM-10871 - [Alerting]: Fixed broken Percona Alerting link on the Settings > Alertmanager integration page. The link now correctly redirects to the Alerting page.
• PMM-11049 - Fixed a typo that was present in enhanced metrics scraper for rds_exporter.
• PMM-11137 - An issue with the MongoDB exporter not showing the version for MongoDB instance has been resolved.
• PMM-11210 - Whenever a cluster was unavailable or deleted, the K8s cluster list was empty. The issue has been resolved now.
• PMM-11239 - Despite removing pmm-server packages before upgrading PMM server, the packages were still present during upgrade. The issue has been resolved now.
• PMM-11372 - The user interface was broken after PMM was upgraded. This issue has been resolved now.

Known issues

• Starting with PMM 2.34.0, the recommended version for running MySQL cluster is 8.0.27. It's impossible to create MySQL clusters using a version older than 8.0.27. All previously created clusters are not affected and will be migrated without any issues.
• [PMM-11474](https://jira.perco...

v2.33.0

Percona Monitoring and Management 2.33.0

Release date:	Dec 13, 2022
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.

⚠️ Important
PMM upgrade fails for versions prior to 2.33.0. Although there is a workaround, we highly recommend using the latest version of PMM. This ensures that you have access to the latest PMM features and that your environment runs on the latest version of the underlying components with all the bug fixes in place.

Release Highlights

Data loss prevention for PMM server outages

Starting with PMM 2.33.0, we have introduced a new solution to prevent data loss in PMM. A network outage between the PMM server and the client prevented metrics from being collected. As a result, the historical data was lost, which can be useful when analyzing trends, diagnosing problems, or investigating issues from a previous period.

In order to address the problem mentioned above, for the PMM server and PMM client running version 2.33.0, in case of a brief outage or network issue, metrics are stored on the monitored instance until the PMM server is up and running. At this point, the metrics will be pushed to the server. It only applies to PMM Clients that run in push mode, which is the default mode. The same holds when a brief network outage occurs on the client side.

⚠️ Caution
The client node can currently store only 1 GB of offline data. So, for example, if your instance is down for three days, all the data will not be retrieved.

With the implementation of the above feature, we have taken the first step toward PMM HA. Furthermore, we are happy to provide a roadmap for PMM HA implementation, a much-anticipated solution by our users. In the event of a failover, your PMM setup will experience near-zero downtime, and monitoring will continue without any data loss.

To ensure a smooth rollout, PMM HA will be introduced in phases, in line with your requirements and feedback.

⚠️ Important
PMM HA will be rolled out in three stages. Stage one of PMM HA is the implementation to prevent data loss with VictoriaMetrics integration for short outages included as part of PMM 2.33.0. HA stages two and three will be rolled out next year.

The following features/use cases will be covered as part of the various stages of PMM HA:

Stages of PMM HA	Solutions Provided
Stage one (included in PMM 2.33.0)	As an initial step towards preventing data loss, we have developed the following: Prevent data loss with VM integration for short outages
Stage two (will be rolled out in 2023)	As part of PMM HA stage two, we plan to implement the following: HA data sources As part of stage two we will let the users use external data sources, thereby decreasing dependency on the file system.
Stage three (will be rolled out in 2023)	As part of PMM HA stage three, we plan to implement the following: Clusterized HA Clustered PMM will be the focus of stage three. Detailed information will be included in the upcoming release notes.

Guided tour of Percona Alerting

Following the recent improvements to PMM Alerting, we have added a short tutorial to help you explore our streamlined alerting system based on Grafana.
The in-app tutorial automatically pops up when you first open the Alerting page to help you uncover the fundamentals of Percona Alerting.

Restore MongoDB backups easier

Building on the significant improvements for MongoDB Backup Management introduced in the previous release. We are now simplifying the process for restoring physical MongoDB backups.
Starting with this release, you can restore physical backups straight from the UI, and PMM will handle the process end-to-end. Prior to this, you would require to perform additional manual steps to restart your MongoDB database service so that your applications could make use of the restored data.

Components Upgrade

• VictoriaMetrics has been upgraded from 1.77.1 to 1.82.1.
• As part of PMM 2.33.0, Grafana has been updated to 9.2.5, which fixes some critical vulnerabilities. For more information, see Grafana 9.2.5

New Features

• PMM-10889 - Starting with PMM2.33.0, while using the pmm-admin CLI command, you do not have to know the entire command. Just type the initial command and press Tab. The rest of the command will be autocompleted.

  Depending on the shell you are using, add the following to your shells .rc file for autocomplete to work:

  source <(pmm-admin completion -c <your shell>)
  E.g. source <(pmm-admin completion -c bash)

• PMM-10955: [Backup Management]: After restoring a backup, you can now check the time when the restore was finalized. For PITR backups, you can also check the time to which the restore was performed.
  This information is available on the tab Backup > Restores page, in the new Finished at column, and in the PITR timestamp field under the Actions menu.

Improvements

• PMM-7000: [HA]: Staring with PMM 2.33.0, if the PMM Server goes down, metrics will be buffered on the monitored instance until PMM Server goes back online, which is when metrics will get pushed to the PMM Server.

• PMM-10901: [Documentation]: To enable the users to use High Availability easily, we have added exclusive documentation for HA.

• PMM-8516: [Backup Management]: When creating a backup, the Vendor field was not automatically populated in the Back-up on demand dialog. This issue is now fixed.

• PMM-10627: [DBaaS]: You can now create a single node cluster for PSMDB.

• PMM-10855: Avoid massive gRPC messages formatting for disabled log level

• PMM-10903: [DBaaS]: To simplify DBaas, you no longer have to manually enter the Public Address on the PMM Settings > Advanced Settings page. With DBaaS enabled, PMM will automatically detect and populate the Public Address.

• PMM-11085: [Backup Management]: We've removed the Create backup option under All backups page > Actions menu because this option can only create on-demand backups. You can continue to create both on-demand and scheduled backups using the Create backup button on this page.

• PMM-10881: [CVE]: As part of PMM 2.33.0, Grafana was updated to 9.2.5, which fixes some critical vulnerabilities. For more information, see Grafana 9.2.5.

• PMM-10385: Starting with PMM 2.33.0, for MySQL, the Explain tab is supported without the Examples tab. If a query in the Explain tab contains sensitive data, placeholders will replace them.

• PMM-8655: Latest state of agents is now available on the PMM server after the connection is re-established between the client and server.

• PMM-10969: VictoriaMetrics operator has been upgraded from 0.24 to 0.29.0.

• PMM-10554: Postgres collector now provides runtime duration for scrapes at the collector level. As a result, we can identify collectors who take too long. By utilizing this data, corrective action can be taken.

• PMM-10629: [Components Upgrade]: VictoriaMetrics has been upgraded from 1.77.1 to 1.82.1.

Bugs Fixed

• PMM-10858: In specific environments, including AWS, some EPEL repository mirrors did not respond within the time limit defined by pmm-update, currently set to 30 seconds. This was causing supervisord to kill pmm-update-checker, the component responsible for verifying if a newer version of the PMM Server is available for upgrade. This issue has been resolved now.

• PMM-10683: [DBaaS]: While registering a K8s cluster on the Manage Components Versions modal, the versions were not getting unchecked. The issue has now been resolved.

• PMM-11082: When adding RDS MySQL instances to PMM, some queries pertaining to table stats were executed, despite table stats being disabled.

• PMM-10637: Fixed an issue where the queries for some panels on the PostgreSQL Instance Summary dashboards were broken.

• PMM-11029: Whenever the max-query-length parameter was set to 3, 2, or 1, the PMM agent would be terminated. The...

v2.32.0

Percona Monitoring and Management 2.32.0

Release date:	Nov 8, 2022
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.

⚠️ Important
We recommend using the latest version of PMM. This ensures that you have access to the latest PMM features and that your environment runs on the latest version of the underlying components, such as VictoriaMetrics, with all the bug fixes in place.

Release Highlights

The release highlights are also available in video format. Watch the What's new in PMM 2.32 video

Backup Management for MongoDB is now generally available

We are happy to announce that the Backup Management for MongoDB has reached General Availability and is no longer in Technical Preview.

This change comes with significant functionality enhancements and added UX improvements:

• Point-in-time recovery (PITR) restores for MongoDB backups: This enables you to restore Amazon S3-compatible backups from any checkpoint in the past.
• Local client storage: In addition to Amazon S3-compatible, we have now also enabled the Local Client location option, which saves backups on the remote folder mounted to PMM client host.
• Key UX improvements: You can now create on-demand and scheduled backups from the same window instead of using separate modals.
  In addition, we have added more icons and renamed tabs columns to better label the actions available behind important options.

For more information, see the Backup and Restore topic in the documentation.

State-of-the-art new Home dashboard

In our continued effort to enhance user experience, we have added another feather to our cap by replacing the existing home dashboard with a brand new Home dashboard in PMM 2.32.0.

We are releasing this dashboard as the default Home dashboard. This dashboard was released in PMM 2.30.0 as an experimental dashboard. After considering your feedback and working meticulously on this dashboard, we have developed an enhanced version in PMM 2.32.0. Read more in the blogpost.

Highlights of the new Home dashboard include:

• Optimized performance to handle a large number of nodes concurrently
• Scalable to accommodate varying loads at all times
• Easy anomaly detection to check the health of your nodes from the Home dashboard
• Color-coded states on panels for a quick visual representation of the problem areas
• Comprehensive and easy-to-use dashboard to reduce cognitive load

For detailed information, see documentation.

Enhanced main menu

• In PMM 2.32.0, you can easily access all dashboards for monitored services due to the contemporized navigation structure. All the dashboards in the services folder that were not accessible from the main menu are now accessible from the main menu via Other Dashboards. Also, your custom dashboards can be accessed easily from the main menu via Other Dashboards.

  For example, to access the dashboards for MySQL, go to MySQL > Other dashboards.

• Only monitored services are now included in the main menu, enhancing the user experience and minimizing cognitive load to maximize usability.

  For example, you will only see MongoDB dashboards in the main menu if you monitor the MongoDB database rather than all the other dashboards.

New Features

• PMM-9366: [Backup Management]: Added possibility to restore MongoDB PITR backups. This option is available under Backup > All Backups > Actions > Restore this backup for any PITR-type backups available in the table.

• PMM-9368: [Backup Management]: Added support for local client storage: When adding storage locations under Backup > Storage Location, you can now also select Local Client option as the location type for storing future backups.

• PMM-10599, PMM-10503: [Backup Management]: Refactored User Interface for creating backups to enable you to create on-demand and scheduled backups from the same window instead of using separate modals.

• PMM-10470: [Backup Management]: Following the support for MongoDB physical backups introduced in PMM 2.31, we have now added the possibility to restore these backups. Restoring MongoDB physical backups requires additional manual operations after the restore and is only available with Percona Server for MongoDB.

• PMM-10502, PMM-10831: [Backup Management]: Improved User Experience and labels on all four tabs of the Backup section:

  • Added icons to better illustrate failed and successful backups.
  • Added Service Name column to show the service from where the backup was retrieved.
  • Renamed DB Vendor tab to DB Technology.
  • Improved Actions menu with clearer labeled options.

• PMM-10742: [Backup Management]: Extended PMM compatibility with Percona Backup for MongoDB (PBM) to support the latest version, v. 2.0 PBM.

• PMM-10829: [Backup Management]: The backups table under Backup > All Backups now includes a new Location column which displays the service where the backup came from (S3 or Local Storage).

• PMM-8792, PMM-9055, PMM-9056 - PMM 2.32.0 introduces the parameter --max-query-length in the pmm-admin command for MySQL, PostreSQL, and MongoDB databases. It can also be set up through the UI while adding the service. You can see a new input field on the UI, where you can set the value for max-query-length. With these changes, queries longer than 2048 characters are not truncated if this parameter is set to -1 (which means no limit), and the Explain and Examples tabs on the QAN dashboard do not throw an error (PMM-1899). These tabs provide contextual information pertaining to the query, thus enhancing user experience. For more information, see documentation.

• PMM-9545: To monitor Kubernetes clusters, PMM now collects Kubernetes metrics from kube-state-metrics. For more information on kube-state-metrics, see documentation.

  ⚠️ Disclaimer
  This feature is still technical preview and is subject to change. We recommend that early adopters use this feature for testing purposes only.

• PMM-10579: [Dashboard]: Only monitored services are displayed on the main menu for a clean and simple User Interface.

• PMM-10512: [Alerting]: When creating new alert rules. you can now use two new labels (application_name and usename) for pg_stat_activity_ metrics.

Improvements

• PMM-9946: [DBaaS]: To enhance user experience, once PMM is deployed to a Kubernetes cluster and a user wants to use DBaaS, PMM automatically registers that Kubernetes cluster to DBaaS.

• PMM-10733: [DBaaS]: We have moved another step forward in simplifying the use of DBaaS by simplifying the selection of the database version.

• PMM-10723: [DBaaS]: To make the content legible, we have changed the color of the notification block.

• PMM-10156: [Dashboard]: Starting with PMM 2.32.0, we have an enhanced PMM dashboard that gives a birds-eye view of the services, infrastructure, and critical issues (if any).

• PMM-10612: [Dashboard]: You can now easily access all dashboards for monitored services. Dashboards in the services folder (MySQL dashboards) that were not accessible from the main menu are now accessible from Other Dashboards.

• PMM-10695: [Dashboard]: For precision, we have added a unit (%) for the CPU Anomalies panel.

• PMM-10487: [Dashboard]: Our Experimental MongoDB dashboards are now equipped with tooltips to help you understand the information provided in the panels.

• PMM-10692: [Dashboard]: Enhanced the High CPU Usage, High Disk Queue, and High Memory Usage panels to make the troubleshooting process easier and more actionable. Just click the node name on the panel to see the details of the problem.

• PMM-10751: [Dashboard]: For the Vacuum dashboard, when filtering by Service name, the first panel that shows the service name and resol...