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.
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.
- 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
- 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-modeflag 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.
- PMM-7312: Error when accessing Metrics data on Dashboards for large installations
- PMM-7310: VictoriaMetrics consuming 100’s Gb’s of disk in
/tmp/searchResultsin 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 foundif both Security Threat Tool and Integrated Alerting enabled
- PMM-7247: DBaaS: Disk size is always 0 for Percona XtraDB cluster
pg_stat_monitorintegration 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-admin annotatecommand 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
rds_exportercrashes when more than 100 AWS RDS instances added (Thanks to https://github.com/vlinevych for fixing this)
pmm-agentconnection checker does not check authentication for MongoDB
- PMM-7303: Disk Details, Nodes Compare dashboards: ‘Disk Utilization’ description is confusing
- Page updated 2021-02-10