v2.22.0

Percona Monitoring and Management 2.22.0

Date:	September 23, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

• DBaaS (Technical preview): DBaaS users can now use the PMM UI to upgrade existing Clusters to the newer version of the operator without interacting directly with Kubernetes.

New Features

• PMM-8396: Backup Management: Add an ability to specify the number of retries for Scheduled backups before operation fails
• PMM-8079: DBaaS: Percona Operators inside Kubernetes cluster managed by PMM can now be upgraded
• PMM-8077: DBaaS: Show the current version of Operators used in Kubernetes Cluster
• PMM-7924: MySQL Performance Details dashboard: Add "Performance Schema Status Monitoring" chart

Improvements

• PMM-8688: Backup Management: When adding a new Backup, the action button now reads "Create Backup" instead of "Edit" to reflect the action happening
• PMM-8311: Integrated Alerting: Disable edit/delete buttons for Percona-sourced Templates
• PMM-8509: Management of ability to update PMM Server in the same way as this implemented to other Settings for PMM. Users can use API, UI, or docker Environment Variables to change the setting responsible for the Update process. As with all PMM settings, environment variables have higher priority and can't be changed with the API or in the UI.
• PMM-7392: DBaaS: Change Number of Nodes when editing Topology

Bugs Fixed

• PMM-8613: Backup Management: Unable to restore MySQL backup
• PMM-8463: Backup Management: State stuck on "Pending" when creating backup with already existing name
• PMM-8408: DBaaS: Development version of PMM Client was used for monitoring DB Clusters created by DBaaS
• PMM-8584: Wrong CPU metric labels in dashboards for RDS instances
• PMM-8421: Listen-port ignored/removed for external services after server update to PMM 2.19 and higher (Thanks to Rainer Plischke for reporting this issue). Please make sure to upgrade PMM Server to avoid loss of external exporter listen port (PMM-8829) and always upgrade PMM Server before PMM Client (PMM-8854).
• PMM-8703: Custom dashboard prevents PMM Server Docker update from 2.20 to 2.21 (Thanks to Hubertus Krogmann for reporting this issue)
• PMM-7690: AWS discovery and monitoring based on IAM roles is not working

📝 Note
If you have problems upgrading your pmm-2-client packages, try clearing caches with:

sudo apt-get clean

and remove files manually with:

cd /var/cache/apt/archives && sudo rm -rf ./*

v2.21.0

Percona Monitoring and Management 2.21.0

Date:	August 26, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights:

• Custom certificates support: We have added support for custom TLS certificates for remote monitoring of PostgreSQL and MongoDB services, configurable on the command line with pmm-admin or through the UI.

• Backup scheduling with retention (Technical Preview): When scheduling a backup you can now specify how many of the most recent backups to keep. Backups not in this range are automatically deleted to free space for new ones.

• New supported versions:

  • DBaaS functionality now supports Kubernetes Operator for MongoDB version 1.9.0.
  • PMM Client packages now support Debian 11 ("Bullseye").

New Features

• PMM-8158: Backup Management: Delete option — When deleting a backup from Backup Management inventory a new option lets you also delete the data file from storage.
• PMM-8156: Backup Management: Retention — You can now define how many of the most recent scheduled backups to keep.
• PMM-8214: Ability to collect Kubernetes cluster metrics — Collection only, metrics are not currently presented on any PMM dashboard.
• PMM-7477: Support custom TLS certificates when monitoring remote MongoDB instances
• PMM-7888: Custom TLS certificates now allow SSL connections to PostgreSQL instances (Thanks to Jyoti Prakash for reporting this issue)

Improvements

• PMM-8267: Backup Management: Active progress indicator
• PMM-8549: Backup Management: Show loading status on delete window
• PMM-8542: Backup Management: Inform that times should be entered in UTC timezone format
• PMM-8316: DBaaS: PSMDB 1.9 operator support —For what's new see release notes.
• PMM-7612: Integrated Alerting: Validate communication settings 'From' email address format
• PMM-7570: Specify Custom Basic Auth password for Agents when adding Services
• PMM-8560: Add support for Debian 11 ("Bullseye") to pmm-client package
• PMM-7087: Rename custom query file to example-queries-postgres.yml and include warning that the file will be overwritten on upgrade; user should create a copy with a new name to prevent losing metrics collection on future upgrades. (Thanks to Daniel Guzman Burgos for reporting this issue)
• PMM-8568: Use latest CentOS patches for creating OVA, AMI and Azure images
• PMM-5291: Update ClickHouse version from 19.7.5.27 to 21.3-lts
• PMM-8091: Collect and present additional ProxySQL metrics taken from runtime_mysql_servers table

Bugs Fixed

• PMM-8616: Backup Management: No 'Delete from storage' action on backup inventory
• PMM-8543: Backups are not visible after PMM Server upgrade
• PMM-8458: Backup Management: Inconsistent auto-fill of 'Vendor' field with on-demand backup
• PMM-8404: Dashboard image rendering plugin renders image that includes error message
• PMM-7286: Query Analytics can't handle colon character (:) in service names (Thanks to Daniel Guzman Burgos for reporting this issue)
• PMM-7278: mongo_exporter fails to authorize when MongoDB running with authMechanism=MONGODB-X509 (Thanks to Lena D for reporting this issue)
• PMM-8307: Default config limits for allowed connections prevents monitoring large numbers (500+) of DB servers
• PMM-2168: rds_exporter not stopped when all RDS instances are removed or disabled
• PMM-8219: PMM Server update panel "Current version" empty if no internet connectivity
• PMM-8559: Unauthorized error appears while logging in

Known Issues

• Failure to upgrade when using a dashboard with custom tags.

⚠️ Important
In some cases users may not be able to complete the upgrade to 2.21.0 and we have linked this back to dashboards with custom tags. This is to be fixed in our upcoming 2.22.0 release but there are steps (more in the ticket) that you can take if you're already impacted by this:

curl -LJOs https://raw.githubusercontent.com/percona/pmm-server/c2e92bc3aec123affda5f1992c96c95ac74f4a2d/import-dashboards.py
docker cp import-dashboards.py pmm-server:/usr/share/percona-dashboards/
docker exec -it pmm-server chmod a+x /usr/share/percona-dashboards/import-dashboards.py

v2.20.0

Percona Monitoring and Management 2.20.0

Date:	August 3, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

• The Easy-install script for PMM Server is checksum verified.
• PMM will use Grafana 7.5 instead of 7.3. We are also preparing for Grafana 8.
• PostgreSQL monitoring with the pg_stat_monitor plugin enabled exposes new metrics such as Plan Times, WAL Fpi/Bytes/Records.
• For users who deploy PMM Server through the AWS Marketplace, AWS RDS service discovery will be executed without AWS credentials and tuning IAM roles.
• For Backup Management (Technical Preview), we added the ability to schedule backups so you can schedule and see already scheduled backups in the UI.

Important note for users of PMM who started out using the Docker image of 2.16.0

If you installed PMM version 2.16 as a new Docker image and have since used the home dashboard upgrade widget to upgrade to any of 2.17, 2.18, or 2.19, you might experience problems with monitoring the PMM server itself, Remote Monitoring, or RDS/Azure monitoring. If you experience any of these problems, you can simply run the following commands to get your instance working and it will be automatically resolved in the next release:

1. Enter the container: docker exec -it pmm-server bash
2. Roll back pmm2-client package to stable version: yum downgrade -y pmm2-client

Alternatively, you can replace the existing Docker container with a fresh install of the latest release by following the official instructions for an upgrade. (This will guide you through taking a backup of your PMM Server and restoring it after installing a fresh docker image of PMM Server.)

New Features

• PMM-8157: Backup Management: Show scheduled backups – A new view that shows the list of scheduled backups with quick actions to enable/disable, edit, copy, and delete.
• PMM-8155: Backup Management: Scheduling of backups – Support for Backup Scheduling has been added so that users can define backup jobs to run automatically in the future with the option of making the schedules recurring.
• PMM-7010: Option to unregister current node (pmm-admin unregister)

Improvements

• PMM-7552: PMM Server Docker image: Add labels to PMM Server Docker image (Thanks to Nicolas for reporting this issue)
• PMM-8266: PMM Server Docker image: Decommission and remove Prometheus binaries and configuration
• PMM-8040: PMM Server Docker image: Remove yum cache to reduce size of image
• PMM-7809: Grafana upgrade from 7.3.7 to 7.5.7 – Read more at grafana.com
• PMM-8386: Overview text on the Home page is missing PostgreSQL as a supported technology
• PMM-7722: DBaaS: Announce new supported version of operator – Shows that a new version of the operator is available.
• PMM-6278: Modification of MySQL 'Delete' queries to provide 'Explain' information
• PMM-8468: Forbid the use of outdated ciphers for HTTPS protocol on exporters
• PMM-7649: Security Checks: Show "Insufficient access permissions" in UI for non admin users
• PMM-8059: Update Query Analytics UI to clarify estimated results on MySQL 'explain' response where we modified original query
• PMM-8043: Return Service Name in GetCheckResults API response
• PMM-8000: Expose new numbered metrics available in pg_stat_monitor 0.9

Bugs Fixed

• PMM-8299: Backup Management: Remove storage location shows wrong notification – When removing a storage location, PMM presents misleading information to the user in the form of two notification messages for both error and success.
• PMM-8283: Backup Management: Error when removing location with 'force delete' option
• PMM-8064: Dashboards: Size of Temp Files Report Metric value has wrong unit on PostgreSQL Instance Summary Dashboard
• PMM-6981: Dashboards: Wrong version is shown for MariaDB services
• PMM-7738: Integrated Alerting: Alerts for some built-in templates missing service name label
• PMM-6877: mongodb_exporter doesn't recognize being on a mongos host and fills the syslog with replSetGetStatus errors (Thanks to Clyde Shillingford for reporting this issue)
• PMM-7627: Consistent PMM Server log management – Adds consistency to the log management of nginx, postgresql and clickhouse-server, which is now delegated to supervisord. Removes the logrotate daemon from the image.
• PMM-8492: PMM Client version is 2.21.0 inside PMM Server after upgrade from 2.16.0

Known Issues (unfixed problems that you should be aware of)

• PMM-8414: Backup Scheduler not working if user specifies explicit job start time

v2.19.0

Percona Monitoring and Management 2.19.0

Date:	June 30, 2021
Installation:	Installing Percona Monitoring and Management

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

Visit our forum to comment on this release.

Release Highlights

• Backup Management can now be enabled from the UI. Go to Configuration → Settings → Advanced Settings, and you will see it in the Technical Preview section. We also added support for MongoDB services on-demand backup and restore. For now, it only supports ReplicaSet on S3-compatible storage.

• Dashboards improvements

  • There are several community-driven improvements to ProxySQL data collection, with new dashboards to expose such metrics like: Queries Latency histograms and SHUNNED_REPLICATION_LAG state.

  • Fixes for Amazon Aurora service detection on the dashboard, MongoDB ReplicaSet Summary, and other MongoDB memory-related panels.

• Improvements to DBaaS secrets by generating strong passwords for operators. This is an improvement to the Automated Operator Installation released in PMM 2.18, which will greatly enhance security.

New Features

• PMM-7639: Backup Management: Ability to remove Backup Location even if there are some backup artifacts on it
• PMM-7567: Backup Management: Simple backup for MongoDB ReplicaSet
• PMM-7568: Backup Management: Simple restore for MongoDB ReplicaSet

Improvements

• PMM-8112: Dashboards: Collect and present histograms from ProxySQL on Queries Latency dashboard (Thanks to foosinn for helping with this improvement)
• PMM-8081: Dashboards: Add collection and presentation for SHUNNED_REPLICATION_LAG state to proxysql_connection_pool_status (Thanks to spaceform for helping with this improvement)
• PMM-7584: Components Upgrade: VictoriaMetrics 1.53.1 to 1.60.0
• PMM-8001: Better error handling when pg_stat_monitor is an unsupported version
• PMM-7659: DBaaS: Ability to specify the type of connection for DBaaS cluster during DB Cluster creation
• PMM-7828: DBaaS: Select Database Type by default if only one operator is installed
• PMM-8153: Backup Management: Disable 'Restore' button for backups whose service has been deleted

Bugs Fixed

• PMM-7194: 'Share with Percona' option doesn't export data from collapsed panels
• PMM-8060: User cannot add remote instances after OVF/AMI upgrade (previously was Known Issue)
• PMM-7104: Slowlog rotation by pmm-agent causing additional unexpected rotation of binary logs (Thanks to Arthur Tokarchuk for reporting this issue)
• PMM-8125: Error of monitoring GCP based PostgreSQL because of internal database cloudsqladmin
• PMM-6778: Can't specify custom labels during node addition/configuration
• PMM-8090: Multi-request protection breaks metrics gathering (Thanks to Francisco Miguel Biete for fixing this bug)
• PMM-5248: InnoDB TableSpace data is not collected for Percona Server 8
• PMM-4665: User's log file contains error messages about TokuDB and heartbeat despite not being used
• PMM-8014: Error when adding Amazon RDS MySQL with TLS over API
• PMM-3352: Low file descriptors limit (1024) with AMI or OVF images causes errors
• PMM-7948: pmm-admin list reports the wrong Node for External Services
• PMM-6295: Unclear/Incorrect statuses of the pmm-agent when Agent or PMM server went down (Thanks to Mikhail Solovyev for reporting this issue)
• PMM-5917: pmm-agent moves slow logs without checking privileges
• PMM-8021: "Query Analytics" misspelled on left side menu
• PMM-5283: Inconsistency with lengths of Example and Fingerprints in Query Analytics
• PMM-8121: Error message and help for "Remove Service" command is not helpful
• PMM-8196: Additional spaces in email/passwords fields on Sign up/Login pages causes Authentication problems
• PMM-8009: Long First/Last names causes errors when used in Register/Login form
• PMM-8220: Dashboards: Active Time Series Changes on Victoria Metrics dashboard report no data
• PMM-8202: Dashboards: No Amazon Aurora services are available on MySQL Amazon Aurora Details dashboard for selection
• PMM-8085: Dashboards: Wrong units are used in MongoDB dashboards on memory-related panels
• PMM-7154: Dashboards: No data on some panels from MongoDB ReplSet Summary dashboard
• PMM-8115: DBaaS: Delete PSMDB cluster action takes too long
• PMM-7737: DBaaS: Replace all default passwords in operator secrets during installation
• PMM-7970: DBaaS: Confusing message for Cluster name pattern on DB Cluster creation screen
• PMM-7755: DBaaS: Clusters with longer name not initializing
• PMM-7528: DBaaS: Error after Kubernetes cluster destroyed or removed externally to DBaaS
• PMM-8013: Backup Management: Unable to get Backup Artifact list after Service removal

v2.18.0

Percona Monitoring and Management 2.18.0

Date:	June 1, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

The goal for this small release was to eliminate a lot of bugs and complete some features.

• DBaaS

  Added the ability for PMM to install the latest versions of the K8s operator into the K8s cluster. There is no longer any need to install the operator manually. Just connect PMM to your K8s cluster and let PMM do the rest.

• Backup Management

  Backup functionality was released as a Technical Preview feature and will require specific prerequisites from the user side to be installed. Currently, PMM will allow you to:

  • manage storage for backups (S3 only);
  • execute a backup for MySQL and Mongo instances;
  • restore a MySQL backup to the same instance from where it was taken (via the UI).

  Restore in other cases is not yet implemented on the UI.

New Features

• PMM-7509: Integrated Alerting: Pagination for Alerts list

Improvements

• PMM-8029: DBaaS: PSMDB 1.8 operator support
• PMM-7548: Integrated Alerting: Disable edit and delete buttons for templates manually staged by user directly on the file system

Bugs Fixed

• PMM-8053: Better error handling for non-admins who try to access the settings page
• PMM-7941: Wrong replication status for MongoDB Replica Set
• PMM-7302: Webhook usage with max_alerts attribute for Alertmanager configuration causes errors for PMM
• PMM-7224: Instance Overview dashboards behave inconsistently
• PMM-6864: MongoDB Oplog Recovery Window dashboard is broken (Thanks to Clyde Shillingford for reporting this issue)
• PMM-7910: MongoDB Query metrics stops being collected if the cursor is failed once (Thanks to Yann Rouillard for reporting this issue)
• PMM-6451: Passing parameters between Query Analytics and Dashboards is broken
• PMM-5368: Unclear message "Failed to get PMM Server parameter" after configuration (Thanks to Martin Wittwer for reporting this issue)
• PMM-5135: Query Example is often empty for MySQL 8+ (Thanks to Mikhail Solovyev for reporting this issue)
• PMM-8083: Better configuration file checking during configuration
• PMM-7958: Databases cannot be deleted while PostgreSQL is being monitored
• PMM-6553: Slow log size units are not defined in help
• PMM-5931: Graph and values in Query Analytics are identical for TOTAL and case when data is Not Available
• PMM-5538: Heavy Load with Distinct Queries on Slowlog enabled could cause no data being reported
• PMM-8095: The link to the Community section in the PMM footer is broken
• PMM-7982: Query Analytics: Sorting element for the columns is hard to access
• PMM-6676: Terms and Privacy pages opened in the current tab complicates registration process
• PMM-6552: Do not register with server if configuration file fails to create on client
• PMM-6505: Inconsistent style for error messages on Add RDS instance page.
• PMM-8069: Integrated Alerting: Alert template now accepts .yaml extension in addition to .yml when manually staging on the file system
• PMM-7673: Integrated Alerting: Actions column is transparent
• PMM-7916: DBaaS: Wrong required resources when editing a cluster
• PMM-7753: DBaaS: Edit DB Cluster shows wrong values by default
• PMM-7184: DBaaS: Connection column showing different values after deleting DB cluster
• PMM-8088: DBaaS: In case of error, the kubeconfig file is left in the system

v2.17.0

Percona Monitoring and Management 2.17.0

Date:	May 11, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

• Custom certificates help define proper security levels for remotely monitored MySQL instances, including Google Cloud SQL.

• Usability improvements to the External Monitoring UI. When filling parameters, you can enter the parts of an endpoint (scheme, host, path) or let PMM automatically extract them from a URL.

• pg_stat_monitor 0.9.0 support. This change will give you compatibility with the latest version. Support for new features will be in an upcoming release.

• Single-line install of PMM Server on supported Linux distributions (this feature is in Technical Preview).

• DBaaS Changes: (this feature is in Technical Preview)

  • It is easier to experience DBaaS functionality; you can quickly turn it ON/OFF in Advanced settings on the Settings page. (Read more)
  • Database components management will enable PMM administrators to limit users in your organization to specific (admin-approved) database versions in their DBaaS DB Clusters.
  • For PXC clusters created using DBaaS, HAProxy will now be used by default. Please note: Monitoring of the HAProxy in DBaaS will be enabled in an upcoming release.

• Changes to Sign in to Percona Platform. From this release, Registration of the Percona account will be more secure and require additional confirmation.

New Features

• PMM-7863: DBaaS: Ability to specify in K8s configuration the version of HAProxy to be used for DB creation
• PMM-7848, PMM-7847, PMM-7421: Add support for using SSL certificates between pmm-admin and monitored MySQL databases
• PMM-7883: Single-line install of PMM Server on supported Linux distributions - [Technical Preview]
• PMM-7013, PMM-7819: DBaaS: Use HAProxy by default instead of ProxySQL for MySQL DB clusters
• PMM-7356, PMM-7581: DBaaS: Management of available versions of DB components
• PMM-7358, PMM-7576: DBaaS: Management of default versions of DB components

Improvements

• PMM-7572: Add TLS options to mysqld_exporter
• PMM-7783: Support of pg_stat_monitor 0.9.0
• PMM-7064: Integrated Alerting: Presenting severity of the Alert Rule using different colors
• PMM-7946: Better error message on PMM client if server doesn't support HAProxy
• PMM-7932: Usability improvements on UI for adding External Services
• PMM-7641, PMM-7820: Add DBaaS to Technical Preview section and allow user to Enable/Disable via UI
• PMM-7966: Telemetry: Collect enabled/disabled status for Integrated Alerting and Security Threat Tool features

Bugs Fixed

• PMM-7911: DBaaS: Invalid Number of Nodes results in an annoying error message pop-up
• PMM-7884: DBaaS: Fix DB Cluster tab loading
• PMM-7917: PostgreSQL exporter has high CPU usage during Restart
• PMM-8037: User can create a Percona Platform account without proper confirmation
• PMM-7702: DBaaS: Cannot edit already-created PSMDB clusters
• PMM-7991: MySQL Summary panel doesn't exist on MySQL Summary dashboard
• PMM-7939: Inconsistent format of version reporting in pmm-admin
• PMM-7920: PostgreSQL Exporter has increased memory usage with pmm-client 2.15.1 & pmm-server 2.16.0
• PMM-7700: Integrated Alerting: Rule API crashing with more than two parameters or invalid values
• PMM-7616: Integrated Alerting: Incorrect title of the page in a browser
• PMM-7396: Integrated Alerting: Alerts tab error if user deletes Alert Rule which has Firing alerts

v2.16.0

Percona Monitoring and Management 2.16.0

Date:	April 15, 2021
Installation:	Installing Percona Monitoring and Management

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

Important note for users of PMM 2.16.0

If you started using PMM from version 2.16 and have already upgraded to 2.17, 2.18, or 2.19, you might have some problems with PMM Server monitoring, Remove Monitoring, or RDS/Azure monitoring. If you experience a problem, we recommend you upgrade and replace the Docker container by following the official instructions for an upgrade here: https://www.percona.com/doc/percona-monitoring-and-management/2.x/setting-up/server/docker.html#upgrade.

If you can't do this, then you need to perform additional steps after upgrading to 2.20.

1. Enter the container: docker exec -it pmm-server bash
2. Roll back pmm2-client package to stable version: yum downgrade -y pmm2-client

Release Highlights

• Amazon RDS PostgreSQL monitoring

  AWS monitoring in PMM now covers PostgreSQL RDS and PostgreSQL Aurora types. PMM will include them in a Discovery UI where they can be added which will result in node related metrics as well as PostgreSQL database performance metrics. Before this release, this was available only to MySQL-related instances from Amazon RDS.

• Azure Discovery and Node metrics extraction

  Technical Preview: PMM will have the same level of support for Microsoft Azure Database as a Service (DBaaS) as we have for AWS's DBaaS (RDS/Aurora on MySQL or PostgreSQL). You will be able to easily discover and add Azure databases for monitoring by PMM complete with node-level monitoring. This feature is available only if you explicitly activate it on the PMM Settings page. Deactivating it will not remove added services from monitoring, but will just hide the ability to discover and add new Microsoft Azure Services.

  (This is a feature technical preview because we want to release it as soon as possible to get feedback from users. We are expecting to do more work on this feature to make it more API and resource efficient.)

• Security Threat Tool Scheduling - Manage execution and execution intervals

  Security Threat Tool users are now able to control the Security Check execution time intervals for groups of checks, move checks between groups, and disable individual checks if necessary.

• Support for pg_stat_monitor 0.8

  Added compatibility with pg_stat_monitor plugin v 0.8.0. This is not exposing the new features for the plugin in PMM yet, but ensures Query Analytics metrics are collected to the same degree it was with version 0.6.0 of the plugin.

• Consistent support of Technical Preview Features

  Reworked the PMM Settings page to make it clear what features are in Technical Preview vs General Availability (GA) and to simplify activation/deactivation of technical preview features. We also provide a better definition of what a Technical Preview is.

• Migration of Settings and other service pages in PMM from Grafana dashboards

  The PMM Settings page and several others (including Add Instance and Inventory) are being converted to Grafana pages and will no longer be presented as dashboards. Additionally, we're moving the menu to the sidebar navigation for consistency and more flexibility compared to the older menu structure.

• Integrated Alerting improvements

  We released the next stage of improvements in Integrated Alerting functionality of PMM to simplify the usage of the feature. Together with improvements, we continue fixing known bugs in this feature.

• [DBaaS] Resource planning and prediction (Resource calculator)

  Technical preview: While creating a DB cluster a user can see a prediction of the resources this cluster will consume with all components as well as the current total and available resources in the K8s. Users will be warned that if they attempt to create a DB cluster it may be unsuccessful because of available resources in the K8s.

• [DBaaS] PSMDB 1.7.0 operator support

  DBaaS in PMM will be using the recently-released Percona Kubernetes Operator for Percona Server for MongoDB 1.7.0 to create MongoDB clusters.

New Features

• PMM-7313, PMM-7610: Ability to discover and monitor Amazon RDS PostgreSQL instances with collecting PostgreSQL and RDS node metrics (Thanks to Daniel Guzman Burgos for reporting this issue).
• PMM-7345: Expose metrics for all available databases on a PMM monitored PostgreSQL server.
• PMM-7344: Update postgres_exporter version from 0.4.6 to 0.8.0. (See the full list of improvements in the changelog.)
• PMM-7767, PMM-7696: Implement feature flag to enable Microsoft Azure monitoring. Users can use the UI or set an environment variable (ENABLE_AZUREDISCOVER=1) during container creation.
• PMM-7684, PMM-7498: Ability to discover running and supported Microsoft Azure Databases instances in a provided account.
• PMM-7678, PMM-7679, PMM-7676, PMM-7499, PMM-7691: Prepare, modify and use azure_exporter to collect Node related metrics.
• PMM-7681: Use Microsoft Azure metrics on Node/OS-related dashboards to show the metrics on panels.
• PMM-7339: Security Threat Tool: Ability to execute security checks individually and on-demand.
• PMM-7451, PMM-7337: Security Threat Tool: Ability to change intervals for security checks on the PMM Settings page.
• PMM-7772, PMM-7338: Security Threat Tool: Ability to change default execution interval per check.
• PMM-7336: Security Threat Tool: Execute checks based on execution interval they belong to.
• PMM-7335: Security Threat Tool: Ship security check files with predefined execution interval.
• PMM-7748: Add an additional experimental menu for Dashboards on the left side panel.
• PMM-7688: Unify UX and layout of all PMM specific pages like Settings, Add Instance etc.
• PMM-7687: Modify links in menus to ensure both menus are working as expected after dashboard URL change.
• PMM-7705: Simplify display of features in technical preview to easily identify them and their current state.
• PMM-7522, PMM-7511: Integrated Alerting: Improve Notification Channels UX by Pagination for the Notification list.
• PMM-7521, PMM-7510: Integrated Alerting: Improve Alert Rule Templates UX by Pagination on Rule Templates list.
• PMM-7652, PMM-7674, PMM-7503, PMM-7486: DBaaS: While creating the DB cluster see all and available resources in the K8s cluster, such as Disk, CPU & Memory.
• PMM-7508, PMM-7488: DBaaS: See predicted resource usage for selected DB Cluster configuration.
• PMM-7364: DBaaS: Show warning before starting creating the cluster if there are not enough resources in the K8s cluster to create DB Cluster with requested configuration.
• PMM-7580, PMM-7359: DBaaS: Users can select the database version to use during DB Cluster creation.

Improvements

• PMM-7506: Security Threat Tool: Reduce False Positives due to Roles automatically created in PXC with no password but cannot be used to login.
• PMM-7569: Make PMM compatible with pg_stat_monitor 0.8 release.
• PMM-7571:...

v2.15.1

Percona Monitoring and Management 2.15.1

Date:	March 18, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

This patch release fixes performance issues discovered in systems, together with other small fixes.

Bugs Fixed

• PMM-7635: Fix high CPU consumption by Grafana server after upgrade by docker replacement to 2.15.0 with large numbers of services in 'push' mode.
• PMM-7713: Fix high CPU and Memory consumption by Victoria Metrics after upgrade by docker replacement to 2.15.0 with large numbers of services in 'pull' mode.
• PMM-7470: MongoDB exporter IndexStatsCollections is assigned values from wrong flag (intended for 2.15.0, omitted due to missing merge cutoff) (Thanks to Tim for reporting this issue).
• PMM-1531: Metrics not being collected due to rename of MySQL 8 information schema tables.

v2.15.0

Percona Monitoring and Management 2.15.0

Date:	March 01, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

• PMM 1 vs. 2 Parity

  Disable collectors during adding node/service to monitoring

  With this feature users can disable any collector used by PMM to get metrics. When metrics cannot be collected or are no longer needed, disabling the collector(s) prevents PMM from flooding logs and saves infrastructure resources.

  Our vision for PMM collectors is to provide “stop from collecting” functionality to prevent possible harm to the user environment. This “disable” feature is an initial step towards the ideal functionality. The full and flexible management for “What metrics to collect and in what resolution” is slated for future releases.

  External services monitoring

  Since PMM 1.4.0, users had the ability to monitor external services Percona didn’t currently support (e.g., Redis). This blog article from 2018 nicely described external services monitoring at that time. (At that time Percona was not natively supporting a PostgreSQL monitoring service and so this was listed as an external service. Today, PostgreSQL is natively supported by PMM.)

  Until now, PMM 2.x didn’t support external services monitoring. With this release, any non-natively supported by PMM service will now become supported with external services monitoring. You can see the list of possible exporters to be used in https://prometheus.io/docs/instrumenting/exporters/. Natively-supported services will continue to deliver an expanded set of metrics and insights.

  Provide summary information for systems (pt-*-summary actions)

  With the addition of pt-*-summary in PMM 2, users can now view summary information about services and nodes on PMM’s dashboard. This summary information is in the industry common format of pt-*-summary tools output to simplify portability of this data. This format will also be preserved in the snapshot of the dashboard shared with Percona Support to simplify investigations of issues.

  Note: pt-*-summary includes formats for:

  • pt-mysql-summary
  • pt-mongodb-summary
  • pt-pg-summary
  • pt-summary

• HAProxy support by PMM

  Users are able to add HAProxy Services for monitoring in PMM2. The support level of them in PMM will be the same we have for ProxySQL, so they will be presented in Inventory and on Dashboard. This will allow users who use HAProxy in their HA configuration to also have this component monitored by PMM. In future releases PMM will start use HAProxy by default for the DBaaS feature and will also use this functionality to monitor HAProxy.

• DBaaS Preview improvements (Technical Preview)

  From now you will be able to see the progress of internal steps the system makes when executing some operations with DBaaS. The Progress Bar will not be time-related and will present only steps. The Progress Bar component will also reflect the K8s/Operator-related errors to the user, so in the case of errors, you will have the error text on the UI, and no need to use K8s tools to see the error. With the same UI, you will be able to see the latest logs from K8s so they will have even more information about why the error happened.

  Known Limitations: The progress bar will not provide valuable information for the Delete operation (will be in a later version when we’ll change the API with Operators Team), Operation of DB Cluster Modification will have “strange” behavior and will start changes from non-zero values of steps. (This will be modified after API changes.)

New Features

• PMM-4172, PMM-4306, PMM-5784, PMM-7177: Services and Nodes Summary presentation. Present information about DB's and Node status using pt-mysql-summary, pt-mongodb-summary, pt-pg-summary outputs (in API and on Dashboards).
• PMM-7123: Ability to add External Services via the UI in PMM server.
• PMM-6711: Add external-group flag for pmm-admin inventory commands for simpler work with External services.
• PMM-7405: Check connection response format when adding External Service to monitoring.
• PMM-6797: HAProxy monitoring: Ability to add HAProxy services with pmm-admin [inventory] add [service] haproxy command.
• PMM-7487: HAProxy monitoring: Check connection to HAProxy services when adding them for monitoring.
• PMM-7496: HAProxy monitoring: New HAProxy PXC dashboards.
• PMM-6943: HAProxy monitoring: Show HAProxy type services in PMM Inventory.
• PMM-6924: Integrated Alerting: Show 'breadcrumbs' navigation aid on non-dashboard pages as well as Grafana dashboard pages.
• PMM-7294: Integrated Alerting: Pagination for viewing large numbers of Alert Rules.
• PMM-7417: Security Threat Tool: Show list of all available security checks.
• PMM-7418: Security Threat Tool: Ability to disable specific security checks.
• PMM-7419: DBaaS: Ability to see DB Cluster creation/modification logs.
• PMM-7266: DBaaS: Cluster creation progress bar -- You can now see the progress of DBaaS DB cluster creation. (The progress bar is based on the number of back-end technical steps, not the time required to perform the tasks.)

Improvements

• PMM-4679: Docker: :latest tag for pmm-server and pmm-client images has been moved from v1 latest release to v2 latest release. Note: use of the latest tag is not recommended in production environments, instead use :2 tag.
• PMM-7472: Remove Prometheus data source -- If you were using custom dashboards with a specified data source (not using empty to use default one) you may need to edit your dashboards to use the proper data source. PMM is no longer using Prometheus but uses compatible storage for metrics from VictoriaMetrics. We renamed the data source to be more technology-agnostic.
• PMM-6695: Software update: Grafana 7.1.3 to 7.3.7 (See What's new in Grafana 7.2 and What's new in Grafana 7.3.)
• PMM-7471: Software update: VictoriaMetrics 1.52.0 to 1.53.1 (See VictoriaMetrics 1.53.0 and VictoriaMetrics 1.53.1.)
• PMM-6693: API keys usage -- PMM users can now use API keys (generated in Grafana UI) for interaction with PMM server instead of username/password pairs. The API key should have the same level of access (Admin or Viewer) as is required for username/password pairs.
• PMM-7240: DBaaS: Change from Dashboard to Grafana Page -- We changed the DBaaS page from a Grafana Dashboard to a Grafana Page to be better aligned with the DBaaS enable/disable status and avoid confusion when DBaaS is disabled.
• PMM-7328: Security Threat Tool: Download and run checks when activated, immediately, repeating every 24 hours thereafter (Previously, downloading and running new checks happened every 24 hours but the cycle didn't begin when STT was activated.)
• PMM-7329: Security Threat Tool: Hide check results tab if STT is disabled.
• PMM-7331: Security Threat Tool: Failed checks have 'Read more' links with helpful content.
• PMM-7422: Security Threat Tool: View all active and silenced alerts.
• PMM-7257, PMM-7433: Integrated Alerting: Easier-to-read rule details in Alert Rules list (API and UI presentation).
• PMM-7259: Integrated Alerting: Better UI error reporting for disabled Integrated Alerting. (Hint to users how to enable it.)
• PMM-5533: Better indentation of columns in pmm-admin list output.
• PMM-5888: Improve pmm-admin --help descriptions for external services.

...

v2.14.0

Percona Monitoring and Management 2.14.0

Date:	January 28, 2021
Installation:	Installing Percona Monitoring and Management

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

Release Highlights

• Switch to push metrics by default

  In PMM 2.12.0, Percona replaced its metrics collection engine (formerly Prometheus) with VictoriaMetrics. Historically, PMM used a pull method with Prometheus while VictoriaMetrics can operate in either a pull or push method. When PMM 2.12.0 was released, Percona kept the default method as pull. Now with PMM 2.14.0, Percona is shifting the default to push for all newly-added instances. This blog post describes the two methods and why push benefits users. Also, here is a post by Peter Zaitzev of FAQs relating to the move to VictoriaMetrics and the push model. Documentation on the push method is here.

  Note: Installing the 2.14.0 or newer PMM server will change the default behavior on 2.12.0 and 2.13.0 clients from "pull" method to "push" for any newly added services. Existing services will remain in whatever mode they were prior to upgrade.

• DBaaS Preview phase 1.0 (Technical Preview)

  In 2.13.0 we introduced Percona's Database as a Service (DBaaS) which enables non-DBAs (software architects, developers, site reliability engineers, etc.) to perform typical DBA tasks to manage an organization's database environment via user interfaces and automation orchestration. This release contains several enhancements and fixes, many directly from user feedback.

  Note: This capability is feature-flagged and turned off by default. Users require a variable to be passed to PMM to expose this functionality.

• External services presentation on node summary dashboard

  Improvements to the user experience for adding and viewing external services (any data that can be monitored by a Prometheus exporter such as: non-Percona supported databases like Redis, ElasticSearch, Cassandra, etc. or an organization's external application) on the Node Summary dashboard of PMM.

New Features

• PMM-5765: Ability to monitor External Services for situations where PMM Client can't be installed -- Uses a new command pmm-admin add external-serverless. (See pmm-admin.) (This is a Technical Preview feature)
• PMM-7015: DBaaS Preview: Create DB cluster with randomly-generated password
• PMM-7007: Integrated Alerting: Ability to copy (duplicate) alert rules
• PMM-7006: Integrated Alerting: Ability to delete alert rules
• PMM-6941: Integrated Alerting: Ability to delete alert rule templates

Improvements

• PMM-6985: DBaaS: Ability to force unregister Kubernetes cluster
• PMM-7145: 'Push' metrics mode is default when adding services and nodes (All agents collecting data from Services and Nodes will now use PUSH model if not specified explicitly. You will still be able to use --metrics-mode flag to use Pull metrics if needed. All previously set up agents will keep their existing mode. To change these you need to remove and re-add them.)
• PMM-7282: Integrated Alerting: Ability to create rule without channels and filters
• PMM-7226: Integrated Alerting: Validate parameters during rule creation/update
• PMM-7082: Integrated Alerting: Severity levels are color-coded
• PMM-7065: Integrated Alerting: Show rule details for items in Alert Rules list
• PMM-7048: DBaaS: Simplify Cluster creation by moving Create Cluster button to earlier steps
• PMM-6993: Protect against possible problems with EXPLAIN of stored functions in MySQL -- We are fixing possible problems caused by an attempt to analyze queries covered in https://bugs.mysql.com/bug.php?id=67632.

Bugs Fixed

• PMM-7312: Error when accessing Metrics data on Dashboards for large installations
• PMM-7310: VictoriaMetrics consuming 100's Gb's of disk in /tmp/searchResults in PMM 2.13.0
• PMM-5137: Swagger page redirect isn't working
• PMM-7144: DBaaS: Creating DB cluster with same name (Thanks to Beata Handzelova for reporting this issue)
• PMM-7323: DBaaS: 'Remove DB Cluster from Kubernetes Cluster' removes wrong one
• PMM-7251: Integrated Alerting: Error Rule with ID "mysql_version" not found if both Security Threat Tool and Integrated Alerting enabled
• PMM-7247: DBaaS: Disk size is always 0 for Percona XtraDB cluster
• PMM-7178: pg_stat_monitor integration is broken with version 0.6.0 of the plugin
• PMM-7169: Old data (from Prometheus) not deleted when Retention period expires
• PMM-7105: Query Analytics: no 'Example' or 'Explain' data for MariaDB
• PMM-7239: Integrated Alerting: Validate Slack channel names in Notification Channels
• PMM-7213: MySQL InnoDB Details dashboard: remove color-coding on 'Data Buffer Pool Fit' element
• PMM-7167: Some panels not visible when using long time intervals (e.g. 30 days)
• PMM-7133: Incorrect descriptions for data links in dashboards
• PMM-7103: VictoriaMetrics build logs not deleted from PMM Server Docker image
• PMM-6904: pmm-admin annotate command crashes for non-generic node types
• PMM-6902: No query Examples on PostgreSQL 12 with pg_stat_monitor
• PMM-6838: ProxySQL Instance Summary dashboard: Incorrect "Hostgroup Size" formula
• PMM-6490: rds_exporter crashes when more than 100 AWS RDS instances added (Thanks to https://github.com/vlinevych for fixing this)
• PMM-6096: pmm-agent connection checker does not check authentication for MongoDB
• PMM-7303: Disk Details, Nodes Compare dashboards: 'Disk Utilization' description is confusing