Skip to content

Percona Monitoring and Management 2.27.0

Date: April 14, 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 the PMM instance. This ensures that you access the latest features of the underlying components, such as VictoriaMetrics, with all the bug fixes in place. One of the critical features of VictoriaMetrics is stream parsing mode, which enhances the performance of PMM and saves memory when scraping targets expose millions of metrics.

Release Highlights

PMM and Percona Portal Integration

  • Enhanced UX for connecting PMM server to Percona Portal

    To leverage Percona Platform’s recent support for federated identity, PMM now uses access-token authorization for connecting PMM instances to Percona Platform.

    This replaces the former username/password authentication used in PMM 2.26.0 and older versions.

    For more information, see Integrate PMM with Percona Platform.

  • Access to account information for Percona customers

    When you connect your PMM instances to Percona Platform as a Percona customer, you can now check all your Percona Platform account information on the new Entitlements and Support Tickets tab on the main menu.

    For more information, see Check your account information in the online Help.

Advisors

  • Broader database health assessments with Advisors

    With this release, we are renaming Security Checks to Advisors and grouping them according to the functionality and recommendations they provide. To reflect these changes, the old Security Threat Tool option is now called Advisors.

    In addition, we have added new checks for MySQL and MongoDB. To check the list of checks and the tier for which they are available, see Advisor checks for PMM in the Percona Platform online Help.

  • New Paid tier and special Advisor checks for customers

    In addition to Registered Checks, Percona customers who connect PMM to Pecona Platform now also have access to Paid Advisor checks, which offer more advanced database health information.

    For more information, see Working with Advisor checks.

  • Advisor checks have been extended with two new query types: GetDiagnosticData and replSetGetStatus.

  • Improved the documentation around developing checks.

DBaaS

Simplified experience in registering EKS cluster with kubeconfig generated by eksctl.

Components upgrade

  • Grafana: PMM 2.27.0 has now migrated to Grafana 8.3.5. This version of Grafana is loaded with a gamut of exciting features. For more information, see What’s new in Grafana v8.0.
  • VictoriaMetrics: VictoriaMetrics has been upgraded to 1.72.0.

New Features

  • PMM-9718: PMM and Percona Portal Integration: Federated connections to Percona Platform.

  • PMM-9305, PMM-8661: PMM and Percona Portal Integration: Visibility over Percona Platform Entitlements and Support Tickets.

  • PMM-9473: Advisors: Additional abilities for MongoDB Advisor Checks.

  • PMM-8800: DBaaS: With PMM, you can now have a simplified experience in registering your EKS cluster with kubeconfig generated by eksctl. Copy-paste the configuration by selecting Using Amazon Elastic Kubernetes Service (EKS) checkbox, and your K8s cluster is registered. For more information, see Documentation.

  • PMM-8434: Support for passing PMM Server Public Address as an environment variable while starting the PMM server. For more information, see Documentation.

Improvements

  • PMM-9319: PMM and Percona Portal Integration: Synchronized Platform and PMM roles: We have updated PMM permissions to ensure that Administrators of Percona Portal organizations are also granted Admin role in PMM. -

  • PMM-9339: Integrated Alerting: The Use TLS option in webhook settings has been renamed to Show TLS setting to better reflect its functionality.

  • PMM-9182: Integrated Alerting: Added Silence All option for when you want to stop notifications from all alerting rules at once.

  • PMM-9164: Integrated Alerting: You can now use an existing rule as a source for new ones instead of using a template.

  • PMM-9635: Advisors: Extended security checks to Advisors to cover broader database health checks.

  • PMM-9148: QAN: You can now share a link for Query Analytics at the click of a button with the Copy Link.

  • PMM-8045: DBaaS: With this version of PMM, we have added a warning about the deletion of API keys so that the user is forewarned before deleting the API key.

  • PMM-9452: With this release of PMM, we have implemented a simplified password change method for the default admin user using the command line parameter change-admin-password.

  • PMM-9542: PMM now predefines certain flags that allow users to set all other VictoriaMetrics parameters as environment variables. For more information see Documentation.

  • PMM-8794: For consistency, we have implemented a unified 24 hours time format for backup management.

  • PMM-9306: VictoriaMetrics has been upgraded to 1.72.0.

  • PMM-8412: Grafana has been upgraded to 8.x.

  • PMM-9648: With PMM 2.27.0 migrating to Grafana 8.0, the Singlestat Panel has been deprecated and replaced with Stat Panel in Grafana for an enhanced user experience.

Bugs Fixed

  • PMM-9797: Fixed an issue where the data on the Home Dashboard was represented incorrectly on the Stat Panel, which could potentially confuse the user.

  • PMM-9757: Fixed an issue where the metrics for MongoDB were not being exposed when the database connection was getting lost.

  • PMM-9603: PMM and Percona Portal Integration: Fixed “Insufficient access rights” error that was displayed for admin user after connecting PMM server connect to Percona Portal.

  • PMM-9323: PMM and Percona Portal Integration: Ensured PMM no longer downloads checks and templates from Percona Portal when the Telemetry option is disabled in the PMM Advanced Settings.

  • PMM-8986: Advisors: Fixed an issue where the Advisors check on the PMM servers monitoring a large number of database services was causing a timeout.

  • PMM-9570: DBaaS: Create DB Cluster dialog box was closing automatically while trying to create a database cluster and had to be opened twice. This issue has been fixed now.

  • PMM-9496: DBaaS: Fixed an issue where the host and database were not being monitored in DBaas.

  • PMM-9783: QAN: Fixed an issue where QAN failed to work after an upgrade.

  • PMM-9661: QAN: Fixed an issue where QAN layout breaks while resizing the window.

  • PMM-9797: Dashboard: Fixed an issue where the data on the Home Dashboard was represented incorrectly on the Stat Panel, which could potentially confuse the user.

  • PMM-9757: Fixed an issue where the metrics for MongoDB were not being exposed when the database connection was getting lost.

  • PMM-9671: Fixed an issue where an upgrade to 2.26.0 failed as PMM crashed.

  • PMM-9413: Fixed an issue where the PMM management daemon was getting deadlocked when a PMM agent was getting connected with a duplicate agent_id.

  • PMM-9015: Fixed an issue where PMM does not display when PostgreSQL is down, thus failing to capture the metrics for PostgreSQL.

  • PMM-8203: Fixed an issue where the pmm-agent.log is cluttered with unnecessary errors when MariaDB database versions 10.2, 10.3, 10.4, and 10.5 are added for monitoring.

  • PMM-5831: Fixed an issue where pmm-admin uses the default value of ‘listen port’ rather than picking up the value from the agent configuration file.

  • Fixed the following CVE’s:

    • PMM-9726: Fixed a critical CVE that was affecting some versions of Go.
    • PMM-9722: Fixed a CVE for ClickHouse DBMS.
    • PMM-9327: Fixed a vulnerability in the Network Security Services (NSS) package.
    • PMM-9502: Fixed multiple JavaScript Common Vulnerabilities and Exposures (CVE) for PMM AMI setup.

Known Issues

PMM-9992: Error while using reverse proxy (like Nginx)

While using a reverse proxy (for example, Nginx) in front of PMM, you can run into the error origin not allowed after upgrading to PMM 2.27.0 or newer versions.

Solution

Add the Host header to the reverse proxy config file.

Example

For Nginx, add the following:

proxy_set_header Host $http_host;


Last update: 2022-06-16