diff --git a/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable-Error.jpg b/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable-Error.jpg index 927414db40..92e6fb8b7e 100644 Binary files a/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable-Error.jpg and b/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable-Error.jpg differ diff --git a/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable.jpg b/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable.jpg index 4a83220493..3fcb7707c7 100644 Binary files a/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable.jpg and b/docs/_images/PMM_Backup_Management-MongoDB-PITR-Enable.jpg differ diff --git a/docs/_images/PMM_Backup_Management-MongoDB-PITR-Inventory.jpg b/docs/_images/PMM_Backup_Management-MongoDB-PITR-Inventory.jpg index c4e45081a1..4d7033ae76 100644 Binary files a/docs/_images/PMM_Backup_Management-MongoDB-PITR-Inventory.jpg and b/docs/_images/PMM_Backup_Management-MongoDB-PITR-Inventory.jpg differ diff --git a/docs/_images/PMM_Backup_Management.jpg b/docs/_images/PMM_Backup_Management.jpg index 469de0e61b..be10ec41cc 100644 Binary files a/docs/_images/PMM_Backup_Management.jpg and b/docs/_images/PMM_Backup_Management.jpg differ diff --git a/docs/_images/PMM_Backup_Management_Scheduled_Backups_Copy.jpg b/docs/_images/PMM_Backup_Management_Scheduled_Backups_Copy.jpg new file mode 100644 index 0000000000..bab898b232 Binary files /dev/null and b/docs/_images/PMM_Backup_Management_Scheduled_Backups_Copy.jpg differ diff --git a/docs/_images/PMM_Home_Dashboard.png b/docs/_images/PMM_Home_Dashboard.png index 9f56704263..9402abdd9f 100644 Binary files a/docs/_images/PMM_Home_Dashboard.png and b/docs/_images/PMM_Home_Dashboard.png differ diff --git a/docs/_images/PMM_Home_Dashboard_Numbered.png b/docs/_images/PMM_Home_Dashboard_Numbered.png index 27d6f0d69d..f4441840fd 100644 Binary files a/docs/_images/PMM_Home_Dashboard_Numbered.png and b/docs/_images/PMM_Home_Dashboard_Numbered.png differ diff --git a/docs/_images/PMM_Home_Dashboard_Numbered_old.png b/docs/_images/PMM_Home_Dashboard_Numbered_old.png new file mode 100644 index 0000000000..27d6f0d69d Binary files /dev/null and b/docs/_images/PMM_Home_Dashboard_Numbered_old.png differ diff --git a/docs/_images/dots-three-vertical.png b/docs/_images/dots-three-vertical.png new file mode 100644 index 0000000000..f5ad8a0fd3 Binary files /dev/null and b/docs/_images/dots-three-vertical.png differ diff --git a/docs/details/commands/pmm-admin.md b/docs/details/commands/pmm-admin.md index fe85818f6b..5ddaf44104 100644 --- a/docs/details/commands/pmm-admin.md +++ b/docs/details/commands/pmm-admin.md @@ -346,6 +346,15 @@ When you remove a service, collected data remains on PMM Server for the specifie - `push`: agent will push metrics. - `pull`: server scrapes metrics from agent. + `--max-query-length=NUMBER` (This parameter is available starting with PMM 2.32.0.) + : Limit query length in QAN. Allowed values: + - -1: No limit. + - 0: Default value. The default value is 2048 chars. + - >0: Query will be truncated after chars. + + !!! caution "" + Ensure you do not set the value of `max-query-length` to 1, 2, or 3. Otherwise, the PMM agent will get terminated. + ##### Advanced Options : PMM starts the MongoDB exporter by default only with `diagnosticdata` and `replicasetstatus` collectors enabled. @@ -560,6 +569,15 @@ In low resolution we collect metrics from collectors which could take some time: - `push`: agent will push metrics. - `pull`: server scrapes metrics from agent. + `--max-query-length=NUMBER` (This parameter is available starting with PMM 2.32.0.) + : Limit query length in QAN. Allowed values: + - -1: No limit. + - 0: Default value. The default value is 2048 chars. + - >0: Query will be truncated after chars. + + !!! caution "" + Ensure you do not set the value of `max-query-length` to 1, 2, or 3. Otherwise, the PMM agent will get terminated. + #### PostgreSQL `pmm-admin add postgresql [FLAGS] [node-name] [node-address]` @@ -627,6 +645,15 @@ In low resolution we collect metrics from collectors which could take some time: - `push`: agent will push metrics. - `pull`: server scrapes metrics from agent. + `--max-query-length=NUMBER` (This parameter is available starting with PMM 2.32.0.) + : Limit query length in QAN. Allowed values: + - -1: No limit. + - 0: Default value. The default value is 2048 chars. + - >0: Query will be truncated after chars. + + !!! caution "" + Ensure you do not set the value of `max-query-length` to 1, 2, or 3. Otherwise, the PMM agent will get terminated. + #### ProxySQL `pmm-admin add proxysql [FLAGS] [node-name] [node-address]` diff --git a/docs/details/dashboards/dashboard-home-experimental.md b/docs/details/dashboards/dashboard-home-experimental.md deleted file mode 100644 index 59ed135e97..0000000000 --- a/docs/details/dashboards/dashboard-home-experimental.md +++ /dev/null @@ -1,56 +0,0 @@ -# Experimental Home Dashboard - -![!image](../../_images/PMM_Home_Dashboard_Experimental.png) - - -The experimental Home Dashboard provides a high level view of your environment. - -This new Home Dashboard displays data that is organized in panels as given below. - - -## Overview - -This panel lists all added hosts along with essential information about their performance. For each host, you can find the current values of the following metrics: - -* CPU Busy -* Memory Available -* Disk Reads -* Disk Writes -* Network IO -* DB Connections -* DB QPS -* Virtual CPUs -* RAM -* Host Uptime -* DB Uptime - -## Anomaly Detection - -This panel lists all the anomalies such as: - -* CPU anomalies -* High CPU servers -* Disk Queue anomalies -* High disk queue - -## Command Center - -This panel provides critical information such as CPU utlization, memory utilization, anomalies, read and write latency, etc., for your environment. - -## Service Summary - -This panel provides the following information for the services being monitored: - -* DB connections -* DB QPS (Query per sec) -* DB uptime - - - - - - - - - - diff --git a/docs/details/dashboards/dashboard-home.md b/docs/details/dashboards/dashboard-home.md index 7b16a05104..2b21af7682 100644 --- a/docs/details/dashboards/dashboard-home.md +++ b/docs/details/dashboards/dashboard-home.md @@ -1,28 +1,24 @@ # Home Dashboard -![!image](../../_images/PMM_Home_Dashboard.png) - -The Home Dashboard is a high-level overview of your environment, the starting page of the PMM portal from which you can open the tools of PMM, and browse to online resources. - -On the PMM home page, you can also find the version number and a button to update your PMM Server. +!!! note alert alert-primary "Availability" + The new Home dashboard is available starting with PMM 2.32.0. -## General Information +The Home Dashboard provides a high-level overview of your environment, such as the services, infrastructure, and critical issues (if any). It is the starting page of PMM from which you can open the tools of PMM and browse online resources. -This section contains links to online resources, such as PMM documentation, releases notes, and blogs. +This Home Dashboard displays data that is organized in panels as given below. -## Shared and Recently Used Dashboards -This section is automatically updated to show the most recent dashboards that you worked with. It also contains the dashboards that you have bookmarked. +![!image](../../_images/PMM_Home_Dashboard.png) -## Statistics -This section shows the total number of hosts added to PMM and the total number of database instances being monitored. This section also displays the current version number. Use the *Upgrade to X.X.X version* to upgrade to the most recent version of PMM. +## Overview -## Environment Overview +This panel lists all added hosts along with essential information about their performance. For each host, you can find the current values of the following metrics: -This section lists all added hosts along with essential information about their performance. For each host, you can find the current values of the following metrics: -* CPU Busy +* Monitored DB Services +* Monitored DB Instances +* Monitored Nodes * Memory Available * Disk Reads * Disk Writes @@ -33,3 +29,48 @@ This section lists all added hosts along with essential information about their * RAM * Host Uptime * DB Uptime +* Advisors check + + This panel also displays the current version number. Use **Upgrade to X.X.X version** to upgrade to the most recent version of PMM. + + +## Anomaly Detection + +The **Anomaly Detection** panel lists all the anomalies in your environment. Color-coded states on the panels provide a quick visual representation of the problem areas. + +The following anomalies are displayed on this panel: + +* CPU anomalies (high as well as low) +* High CPU servers +* Low CPU servers +* Disk Queue anomalies +* High disk queue +* High Memory Used + + +## Command Center + +You can find critical information such as CPU utlization, memory utilization, anomalies, read and write latency, etc., about your environment on the **Command Center** panel. + +The information is represented graphically on the **Command Center** panel. In this panel, the graphs for the last hour and the previous week are displayed adjacently, making it easy to identify the trends. + +The following information is displayed on the **Command Center** for the **Top 20** nodes: + +* CPU usage +* Disk queue +* Disk Write latency +* Disk Read latency +* Memory usage + +Command Center lists the + +## Service Summary + +The Service Summary panel provides the following information for the services being monitored: + +* DB connections +* DB QPS (Query per sec) +* DB uptime + + + diff --git a/docs/details/dashboards/index.md b/docs/details/dashboards/index.md index edaf9b7100..9b72c59db7 100644 --- a/docs/details/dashboards/index.md +++ b/docs/details/dashboards/index.md @@ -4,7 +4,6 @@ |-------------------|------------------------------------------------------------------------------------------|:-------------------------------------:| | Insight | [Advanced Data Exploration] | 7 | Insight | [Home Dashboard] | 26 -| Insight | [Experimental Home Dashboard] | 26 | Insight | [Prometheus Exporter Status] | 57 | Insight | [Prometheus Exporters Overview] | 27 | Insight | [VictoriaMetrics] | 52 @@ -64,7 +63,6 @@ [Advanced Data Exploration]: dashboard-advanced-data-exploration.md [Home Dashboard]: dashboard-home.md -[Experimental Home Dashboard]: dashboard-home-experimental.md [DB Cluster Summary]: dashboard-cluster-summary.md [Prometheus Exporter Status]: dashboard-prometheus-exporter-status.md [Prometheus Exporters Overview]: dashboard-prometheus-exporters-overview.md diff --git a/docs/details/interface.md b/docs/details/interface.md index 4117929845..03a7fec907 100644 --- a/docs/details/interface.md +++ b/docs/details/interface.md @@ -87,6 +87,9 @@ This menu bar is context-sensitive; it changes according to the page you are on. | Service Name | Filter by service name. | PMM Annotations | View [annotations](../how-to/annotate.md). +## Shortcut menu + +This menu contains shortcut for *Home*, *Query Analytics*, *Services*, and *PMM*. ### Services menu @@ -100,6 +103,11 @@ The *Services* menu choice determines the Service Type menu. | | Nodes Overview | OS | OS dashboards. | | PostgreSQL Instances Overview | PostgreSQL | PostgreSQL dashboards. + +!!! hint alert alert-success "Note" + - You can easily access all dashboards for monitored services from the *Main menu* via *Other Dashboards* in the *Services* sub menu. + - Only the services being monitored by PMM will appear on the main menu. + ### PMM menu This item lists shortcuts to utility pages. diff --git a/docs/release-notes/2.32.0.md b/docs/release-notes/2.32.0.md new file mode 100644 index 0000000000..74ed4839a2 --- /dev/null +++ b/docs/release-notes/2.32.0.md @@ -0,0 +1,159 @@ +# Percona Monitoring and Management 2.32.0 + +| **Release date:** | Nov 8, 2022 | +| ----------------- | ----------------------------------------------------------------------------------------------- | +| **Installation:** | [Installing Percona Monitoring and Management](https://www.percona.com/software/pmm/quickstart) | + +Percona Monitoring and Management (PMM) is an open source database monitoring, management, and observability solution for MySQL, PostgreSQL, and MongoDB. + +!!! caution alert alert-warning "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 + +### MongoDB Backup Management 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 backups from any checkpoint in the past. +- **Local client storage**: In addition to Amazon S3, 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](https://docs.percona.com/percona-monitoring-and-management/using/backup.html) 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](https://www.percona.com/blog/percona-monitoring-and-management-home-dashboard-whats-new/). + +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](https://docs.percona.com/percona-monitoring-and-management/details/dashboards/dashboard-home.html) + +### 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](https://jira.percona.com/browse/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](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-10599), [PMM-10503](https://jira.percona.com/browse/PMM-10599): [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](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-10502), [PMM-10831](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-10742): [Backup Management]: Extended PMM compatibility with Percona Backup for MongoDB (PMB) to support the latest version, v. 2.0 PBM. +- [PMM-10829](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-8792), [PMM-9055](https://jira.percona.com/browse/PMM-9055), [PMM-9056](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-1899)). These tabs provide contextual information pertaining to the query, thus enhancing user experience. For more information, see [documentation](https://docs.percona.com/percona-monitoring-and-management/details/commands/pmm-admin.html) + + +- [PMM-9545](https://jira.percona.com/browse/PMM-9545): To monitor Kubernetes clusters, PMM now collects Kubernetes metrics from kube-state-metrics. For more information on kube-state-metrics, see [documentation](https://github.com/kubernetes/kube-state-metrics). + + + !!! caution alert alert-warning "Disclaimer" + This feature is still [technical preview](../details/glossary.md#technical-preview) and is subject to change. We recommend that early adopters use this feature for testing purposes only. + + + +- [PMM-10579](https://jira.percona.com/browse/PMM-10579): [Dashboard]: Only monitored services are displayed on the main menu for a clean and simple User Interface. +- [PMM-10512](https://jira.percona.com/browse/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](https://jira.percona.com/browse/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](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-10723): [DBaaS]: To make the content legible, we have changed the color of the notification block. + +- [PMM-10156](https://jira.percona.com/browse/PMM-10156): [Dashboard]: Starting with PMM 2.32.0, we have an enhanced PMM dashboard that gives a bird-view of the services, infrastructure, and critical issues (if any). + - [PMM-10612](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-10695): [Dashboard]: For precision, we have added a unit (%) for the CPU Anomalies panel. + +- [PMM-10487](https://jira.percona.com/browse/PMM-10487): [Dashboard]: Our Experimental MongoDB dashboards are now equipped with tooltips to help you understand the information provided in the panels. + +- [PMM-10692](https://jira.percona.com/browse/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](https://jira.percona.com/browse/PMM-10751): [Dashboard]: For the Vacuum dashboard, when filtering by Service name, the first panel that shows the service name and resolution was hidden due to the Disclaimer. It has now been moved above the Disclaimer to make it readable. + + +- [PMM-10690](https://jira.percona.com/browse/PMM-10690): [Dashboard]: Starting with PMM 2.32.0, we have enabled sparklines for Disk Read and Write panels to visually represent and show trends in the data. + +- [PMM-10697](https://jira.percona.com/browse/PMM-10697): [Dashboard]: We have improved the visualization of the Used Memory Anomaly Panel on the Home Dashboard so that all the anomalies are visible. + +- [PMM-10694](https://jira.percona.com/browse/PMM-10694): [Dashboard]: Added and refined tooltips for all the panels on the dashboard. + + +- [PMM-10721](https://jira.percona.com/browse/PMM-10721): On the **Explore dashboard**, **Metrics panel**, removed the links pointing to the Grafana discussion board. + +- [PMM-10662](https://jira.percona.com/browse/PMM-10662), [PMM-10633](https://jira.percona.com/browse/PMM-10633), [PMM-10631](https://jira.percona.com/browse/PMM-10631), [PMM-10600](https://jira.percona.com/browse/PMM-10600): An additional MySQL and MongoDB related datapoints have been fadded to Telemetry. + + +- [PMM-10926](https://jira.percona.com/browse/PMM-10926): [Backup Management]: Updated the documentation with information about required user permissions for creating Mongo BM backups. For more information, see the [MongoDB topic](https://docs.percona.com/percona-monitoring-and-management/setting-up/client/mongodb.html#create-pmm-account-and-set-permissions). + +- [PMM-10393](https://jira.percona.com/browse/PMM-10393): The panel for total time taken for scraping metrics by Postgres exporter is improved. Instead of showing coarse-grained measurements of the total time taken by the exporter, it now shows the total time taken per collector. + +- [PMM-10555](https://jira.percona.com/browse/PMM-10555): Runtime for collectors in MongoDB exporter is pushed via Telemetry to PMM. This information detects considerable scrape time for collectors and improves collector performance in future releases. + + +## Bugs Fixed + +- [PMM-10944](https://jira.percona.com/browse/PMM-10944): [Backup Management]: Fixed an issue that was preventing QAN to retrieve data after a restore for MongoDB with authentication enabled. + +- [PMM-10840](https://jira.percona.com/browse/PMM-10840): [Alerting]: Fixed embedded templates that are using expressions like **x == 0** or **x != 0**. +PMM servers connected to Percona Platform already include this fix, since Percona Platform delivered it via Automatic Template Updates, a couple of weeks ago. + +- [PMM-10759](https://jira.percona.com/browse/PMM-10759): [Alerting]: Renamed the **Alerting** option in the PMM Settings to **Percona Alerting**. Since this option refers to Percona Alert Rule Templates, this new label reflects better the fact that this option is different from the basic, built-in Alerting functionality. + +- [PMM-10810](https://jira.percona.com/browse/PMM-10810): [Alerting]: Fired alerts now show the correct summary, which includes the node or service name specified in the template annotations. + +- [PMM-10500](https://jira.percona.com/browse/PMM-10500): [DBaaS]: DBaaS: Fixed an issue where a database cluster for an unregistered k8s cluster was still being displayed on the UI. + +- [PMM-10640](https://jira.percona.com/browse/PMM-10640): [DBaaS 1.10, 1.11]: Fixed an issue where a MongoDB 5.0.x cluster was not getting created. + +- [PMM-9874](https://jira.percona.com/browse/PMM-9874): [Dashboard]: Fixed an issue where the current ReplSet State stat is unreadable after modifying or restarting the database cluster for MongoDB Dashboard. + +- [PMM-10339](https://jira.percona.com/browse/PMM-10339): [Dashboard]: Fixed the duplicate values displayed on the CPU usage charts for MongoDB and MySQL dashboards. + + +- [PMM-10802](https://jira.percona.com/browse/PMM-10802): [Advisors]: Fixed **MongoDBGetDiagnosticData** and **MongoDBReplSetGetStatus** query type for Advisors Checks V2. + + +- [PMM-10688](https://jira.percona.com/browse/PMM-10688): This bug fix restores the ability to copy existing kubeconfig and register a new cluster by provided copy. However, AWS secrets will be hidden in the UI. + +## Known Issues + +[PMM-11029](https://jira.percona.com/browse/PMM-11029): **pmm-agent: killed when --max-query-length <=3** + +If the value of the parameter `max-query-length` is set to 3, 2 or 1, the PMM agent will get terminated. + +**Solution** + +The value of the parameter should be greater than 3. + + diff --git a/docs/release-notes/index.md b/docs/release-notes/index.md index 6518fd98db..cd546288cb 100644 --- a/docs/release-notes/index.md +++ b/docs/release-notes/index.md @@ -1,4 +1,5 @@ # Release Notes +- [Percona Monitoring and Management 2.32.0](2.32.0.md) - [Percona Monitoring and Management 2.31.0](2.31.0.md) - [Percona Monitoring and Management 2.30.0](2.30.0.md) - [Percona Monitoring and Management 2.29.1](2.29.1.md) diff --git a/docs/using/backup.md b/docs/using/backup.md index 186ed3d654..88ad9994bd 100644 --- a/docs/using/backup.md +++ b/docs/using/backup.md @@ -1,31 +1,42 @@ -# Backup and Restore - -!!! caution alert alert-warning "Caution" - - Backup and restore are [technical preview](../details/glossary.md#technical-preview) features. - - Currently supported: MySQL database server or MongoDB replica set cluster, backing up to Amazon AWS S3 storage locations. - -!!! summary alert alert-info "Summary" - - [Enable backup features](#before-you-start). - - [Add a storage location]. - - Satisfy preconditions: - - For [MySQL](#mysql-backup-preconditions): - - Confirm instance service parameters and storage location. - - Install required packages. - - For [MongoDB](#mongodb-backup-preconditions): - - Install and run [Percona Backup for MongoDB] on every node in the replica set. - - [Make a backup](#make-a-backup), or, - - [Make](#make-a-scheduled-backup) or [edit](#edit-a-scheduled-backup) a scheduled backup, or, - - [Enable MongoDB Point-In-Time-Recoverable Backups](#mongodb-point-in-time-recoverable-backups), or, - - [Restore a backup](#restore-a-backup). - - [Delete a backup](#delete-a-backup). - -## Before you start - -- You have an AWS S3 storage account and location details for it. - - !!! note alert alert-primary "" - In addition to bucket location details, you will also need to ensure proper S3 permissions. General minimum permissions - are LIST/PUT/GET/DELETE. A sample IAM policy is: +# Backup and restore + +## Supported setups + +**- MySQL database server with support for:** + + - Creating and restoring physical backups + - Storing backups to Amazon S3 + +**- MongoDB replica set setups with support for:** + + - Storing backups on Amazon S3 and on mounted filesystem + - Creating and restoring Logical snapshot backups + - Creating and restoring Physical snapshot backups. This is only available with Percona Server for MongoDB and requires post-restore actions. + - Creating logical PITR backups both locally and on S3. Restoring logical PITR backups from S3. + + For a detalied overview of the supported setups for MongoDB, check out the [Support matrix](../using/mongodb_limitations.md). + +## Prerequisites + +### Enable Backup Management + 1. Go to **Configuration > PMM Settings > Advanced Settings** and activate the **Backup Management** option. + 2. Click **Apply changes**. This adds the Backup option on the side menu. + +!!! caution alert alert-warning "Important" + If PMM Server runs as a Docker container, enable backup features at container creation time by adding `-e ENABLE_BACKUP_MANAGEMENT=1` to your `docker run` command. + +### Prepare a storage location +#### For local backups +If you prefer storing your backup artifacts on a remote filesystem, make sure that you have Write permissions on the path you define, and that you've mounted the remote folder to all the mongoDB nodes. + +For more information, see the [Percona Backup for MongoDB (PBM) documentation](https://www.google.com/url?q=https://docs.percona.com/percona-backup-mongodb/details/storage-configuration.html%23remote-filesystem-server-storage&sa=D&source=docs&ust=1667855380308508&usg=AOvVaw3B1N4tjh_mv8lt4msbf3Ui). + +#### For Amazon AWS S3 backups +If you want to store backup artifacts in the cloud, make sure you have your Amazon S3 storage account and location details ready. +In addition to bucket location details, you will also need to ensure proper S3 permissions. + +The general minimum permissions are **LIST**/**PUT**/**GET**/**DELETE**. +A sample IAM policy is: ```json { @@ -52,49 +63,24 @@ ] } ``` + +### [Create a storage location](#create-a-storage-location) - -- Backup management has been enabled: - - 1. Select *Configuration* → *Settings* → *Advanced Settings*. - - 1. Activate *Backup Management*. - - 1. Click *Apply changes*. - - !!! note alert alert-primary "" - If PMM Server runs as a Docker container, enable backup features at container creation time by adding `-e ENABLE_BACKUP_MANAGEMENT=1` to your `docker run` command. - -## Add a storage location - -1. Select → *Backup*. - -1. Select *Storage locations*. - +1. Go to **Backup > Storage Locations**: ![!](../_images/PMM_Backup_Management.jpg) -1. Click *Add*. +2. Click **Add storage location** and fill in a name and description for this new location. +3. Choose the type of storage location you are creating: + - **S3**: Specify the Amazon AWS S3 backup location endpoint (URL), bucket name, and connection details. + - **Local Client**: specify the path on your local client for files to be backed up to. -1. Fill in the form fields. +4. Optionally, click **Test** to test the connection. - ![!](../_images/PMM_Backup_Management_Locations_Add_Storage_Location.jpg) +5. Click **Add** to create the location. - - *Name*: A short name for this location. - - *Description*: A long description for this location. - - *Type*: Choose the type of storage: - - *S3*: Use [Amazon AWS S3] - - *Endpoint*: The S3 backup location endpoint (URL). - - *Bucket Name*: The bucket name. - - *Access Key*: The access key string. - - *Secret Key*: The secret key string. (Click to reveal and to hide again.) - - *Local Client:* (Not currently implemented) - - *Local Server:* (Not currently implemented) +### MySQL backup prerequisites -1. (Optional) Click *Test* to test the connection. - -1. Click *Add* to add the location. - -## MySQL backup preconditions +To be able to create MySQL backups, make sure that: - [PMM Client](../setting-up/client/index.md) is installed and running on the node. @@ -126,199 +112,121 @@ - [`qpress`][PERCONA_QPRESS]. - !!! caution alert alert-warning "Important" - The versions of each must be compatible with the installed version of MySQL. +!!! caution alert alert-warning "Important" + The versions of each must be compatible with the installed version of MySQL. -## MongoDB backup preconditions +### MongoDB backup prerequistes -- [Percona Backup for MongoDB] is installed and `pbm-agent` is running on all MongoDB nodes in the replica set. +Before creating MongoDB backups, make sure that: +- [PMM Client](../setting-up/client/index.md) is installed and running at least on one node of replica set (the one which will be used for backup and restore jobs). +- [Percona Backup for MongoDB] (PBM) is installed and `pbm-agent` is running on all MongoDB nodes in the replica set. PMM 2.32 and later require PBM 2.0.1 or newer. - MongoDB is a member of a replica set. - -## Make a backup - -Make a single on-demand backup. - -1. [Add a storage location]. - -1. Select → *Backup*. - -1. Select *Backup Inventory*. - -1. Click *Add*. - -1. In the *Backup on demand* dialog, enter values for: - - - *Service name*: Choose from the menu the service to back up. - - *Vendor*: A value is automatically selected based on the service type. - - *Backup name*: Enter a unique name for this backup. - - *Description*: (Optional) Enter a long description for this backup. - - *Location*: Choose from the menu the storage location. - -1. Click *Backup*. - -1. In the *Backup Inventory* pane, watch the *Status* column. An animated ellipsis indicator {{icon.bouncingellipsis}} shows activity in progress. - -## Make a scheduled backup - -Make regular scheduled backups. - -1. [Add a storage location]. - -1. Select → *Backup*. - -1. Select *Scheduled Backups*. - -1. Click *Add*. - -1. In the *Schedule backup* dialog, enter values for: - - - *Service name*: Choose from the menu the service to back up. - - *Backup name* : Enter a unique name for this scheduled backup. - - *Vendor*: A value is automatically selected based on the service type. - - *Location*: Choose from the menu the storage location. - - *Data model*: Select one of the options: - - *Physical*: Takes a physical backup of the database files. - - *Logical*: Takes a logical backup of data in the database. Currently not supported for MySQL. - - *Description*: (Optional) Enter a long description for this scheduled backup. - - *Schedule*: The schedule for the backup. - - *Every*: The backup interval. Choose from the menu one of: - - *Year* - - *Month* - - *Week* - - *Day* - - *Hour* - - *Minute* - - Depending on the interval chosen, the remaining options will be active or inactive. - - *Month*: Select one or more months. - - *Day*: Select one or more day numbers. - - *Weekday*: Select one or more week day names. - - *Start time, h/m*: The hour and minute for the backup. - - In the first field, select one or more hours (*00* to *23*, *00* is midnight). - - In the second field, select one or more minutes (*00* to *59*). - - - *Retention*: How many backups to keep. For unlimited, use `0` (zero). - - *Retry mode*: In case of error, either let PMM retry the backup again ("Auto") or do it again yourself ("Manual"). - - *Retry times and interval*: If "Auto" retry mode is selected, the maximum number of retries - up to 10 - and the interval between them - up to 8 hours - can be set here. - - *Enable*: Deselect to define the scheduled backup without enabling it. - - ![!](../_images/PMM_Backup_Management_Schedule.png) - - !!! note "" - For this release ({{release}}), times are UTC. - -1. Click *Schedule*. - -1. A new entry will appear in the list. +- Check out the current [MongoDB supported configurations and limitations](mongodb_limitations.md). + +## [Make a backup](#make-a-backup) + +To create a backup: + +1. Go to **Backup > All Backups**. +2. Click **Create Backup**. +3. Specify the type of backup that you want to create: **On Demand** or **Schedule Backup**. +4. Enter a unique name for this backup. +5. Choose the service to back up from the Service name drop-down menu. This automatically populates the **DB Technology** field. +6. Select whether you want to create a **Physical** or **Logical** backup of your data, depending on your use case and requirements. For MySQL, only the **Physical** data model is available. +7. Choose a storage location for the backup. MySQL currently only supports storing backups to Amazon S3. If no options are available here, see the [Create a storage location](#create-a-storage-location) section above. +8. If you're creating a schedule backups, also specify the backup type, the schedule, and a retention policy for your backup: + - **Backup Type**: currently, PMM supports both **Full** and Point-in-type recovery **(PITR)** backup types for MongoDB. However, the PITR option is only available for the **Logical** data model. For MySQL, only the **Full** type is supported. + - **Shedule**: configure the frequency and the start time for this backup. Make sure that the the schedule you specify here does not create overlapping jobs or overhead on the production environment. Also check that your specified shedule does not overlap with production hours. + - **Retention**: this option is only available for Snapshot backups stored on Amazon S3. If you wand to keep an unlimited number of backup artifacts, type `0`. +9. Expand **Advanced Settings** to specify the settings for retrying the backup in case of any issues. You can either let PMM retry the backup again (**Auto**), or do it again yourself **Manual**. Auto retry mode enables you to select up to ten retries and an interval of up to eight hours between retries. +10. Click **Backup** to start creating the backup artifact or schedule a job. +11. Go to the **All Backups** tab, and check the **Status** column. An animated ellipsis indicator {{icon.bouncingellipsis}} shows that a backup is currently being created. ## Edit a scheduled backup -1. Select → *Backup*. - -1. Select *Scheduled Backups*. - -1. In the *Actions* column: +1. Go to **Backup > Scheduled Backup Jobs**. +2. In the **Actions** column: - Click the switch to enable or disable the backup. - - Click to edit the backup schedule. - - Click to delete the backup schedule. - - Click to create a (by default, disabled) copy of the backup schedule. + - Click ![](../_images/dots-three-vertical.png) to edit, delete or create a (by default, disabled) copy of the backup schedule. - ![!](../_images/PMM_Backup_Management_Scheduled_Backups_Copy.png) + ![!](../_images/PMM_Backup_Management_Scheduled_Backups_Copy.png) -## MongoDB Point-In-Time-Recoverable Backups +## MongoDB Point-In-Time-Recoverable Backups (PITR) -!!! caution alert alert-warning "Caution" - - MongoDB Point-In-Time-Recoverable Backups is part of Backup Management which is a [technical preview](../details/glossary.md#technical-preview) feature. +Point-in-Time Recovery restores databases up to a specific moment. PITR includes restoring the data from a backup snapshot and replaying all events that occurred to this data up to a specified moment from [oplog slices]. -### What is it? +Point-in-Time Recovery helps you prevent data loss during a disaster such as crashed database, accidental data deletion or drop of tables, unwanted update of multiple fields instead of a single one. -Better described by our team mates that develop Percona Backup for MongoDB: +### Compatibility with Percona Backup for MongoDB +PMM introduced the option to create PITR Backups for MongoDB in version 2.23, as part of the larger Backup Management feature. This implementation in PMM uses Percona Backup for MongoDB (pbm) behind the scenes. -!!! note alert alert-primary "" - Point-in-Time Recovery is restoring a database up to a specific moment. Point-in-Time Recovery includes restoring the data from a backup snapshot and replaying all events that occurred to this data up to a specified moment from [oplog slices]. Point-in-Time Recovery helps you prevent data loss during a disaster such as crashed database, accidental data deletion or drop of tables, unwanted update of multiple fields instead of a single one. +Percona Backup for MongoDB is a distributed, low-impact solution for achieving consistent backups of MongoDB sharded clusters and replica sets. -Point-In-Time-Recovery (PITR) Backups for MongoDB is new functionality available with PMM 2.23.0 as part of the larger Backup Management feature. This implementation in PMM uses Percona Backup for MongoDB `pbm >= 1.6.0` behind the scenes. +Starting with PMM 2.32, restoring PITR backups is available for backups based on pbm ≤ 2.0.1. To restore PITR backups, make sure you have pbm ≥ 2.0.1 installed. -!!! caution alert alert-warning "" - - Percona Backup for MongoDB is a distributed, low-impact solution for achieving consistent backups of MongoDB sharded clusters and replica sets. Percona Backup for MongoDB supports [Percona Server for MongoDB] and MongoDB Community v3.6 or higher with [MongoDB Replication] enabled. Learn more about [Percona Backup for MongoDB]. + Percona Backup for MongoDB supports [Percona Server for MongoDB](https://www.percona.com/software/mongodb/percona-server-for-mongodb) and MongoDB Community ≤ 3.6, with [MongoDB Replication](https://docs.mongodb.com/manual/replication/) enabled. For more information, see the [Percona Backup for MongoDB documentation](https://docs.percona.com/percona-backup-mongodb/installation.html). ### How does it work? -#### Enabling PITR - -The very first thing you want to do is to enable PITR. Here’s how: +To create a PITR backup, select the **PITR** backup type option when creating scheduled backup for MongoDB. See the [Make a backup](#make-a-backup) section above. -1. Go to *Backup Management*. -1. Select *Scheduled Backups*. -1. Click on *Add* to create a new scheduled backup. -1. Click on the PITR button to enable Point-In-Time-Recovery. +![!](../_images/PMM_Backup_Management-MongoDB-PITR-Enable.jpg) - ![!](../_images/PMM_Backup_Management-MongoDB-PITR-Enable.jpg) -Once you’ve enabled PITR, head to the list of Scheduled Backups to confirm PITR is enabled. +#### PITR artifacts -![!](../_images/PMM_Backup_Management-MongoDB-PITR-Enable-Check.jpg) - -To disable PITR use the corresponding switch available on the list. - -#### PITR Artifacts - -The PITR artifacts will be available once your PITR job has run for the first time. Go to Backup Inventory to see the corresponding PITR artifact. +The PITR oplog is available a few minutes (10 by default) after your PITR job has run for the first time. To see the corresponding PITR artifact, check out the list under **Backup > All Backups**. ![!](../_images/PMM_Backup_Management-MongoDB-PITR-Inventory.jpg) -#### PITR and Other Scheduled Backups +#### PITR and other scheduled backups -It is important to notice that enabling PITR requires any other scheduled backup jobs to be disabled. If you try to enable PITR while other scheduled backup jobs are active, you will be shown an error message as seen in the image below. +Make sure to disable any other scheduled backup jobs before creating a PITR backup. PMM displays an error message if you try to enable PITR while other scheduled backup jobs are active: ![!](../_images/PMM_Backup_Management-MongoDB-PITR-Enable-Error.jpg) -Go ahead to manually disable the existing scheduled jobs, then you’ll be able to enable PITR. - -The above constraint applies at the service level. That said, you can still have PITR enabled for one service while having regular scheduled backup jobs for other services. +This constraint applies at the service-level. You can still have PITR enabled for one service while having regular scheduled backup jobs for other services. ## Restore a backup -!!! note alert alert-primary "" - MySQL backups can be restored to the same service it was created from, or to a compatible one. MongoDB backups can only be restored to the same service it was created from. - -1. Select → *Backup* → *Backup Inventory*. - -1. Find the row with the backup you want to restore. - -1. In the *Actions* column for that row, click *Restore from backup*. - -1. In the *Restore from backup* dialog: +### Restore compatibility +MySQL backups can be restored to the same service it was created from, or to a compatible one. MongoDB backups can only be restored to the same service they were created from. - - Select *Same service* to restore to a service with identical properties. - - Select the service in the *Service name* menu. +To restore a backup: - - Select *Compatible services* to restore to a compatible service. - - Select the compatible service in the *Service name* menu. +1. Go to **Backup > All backups** and find the backup that you want to restore. +2. Click the arrow in the **Actions** column to check all the information for the backup, then click ![](../_images/dots-three-vertical.png) **> Restore from backup**. +3. In the **Restore from backup** dialog, select **Same service** to restore to a service with identical properties or **Compatible services** to restore to a compatible service. +4. Select one of the available service names from the drop-down menu. +5. If you are restoring a PITR backujp, also select the point for the date and time that you want to restore the database to. +6. Check the values, then click **Restore**. +7. Go to the **Restores** tab to check the status of the restored backup. +During restoring, PMM disables all the scheduled backup tasks for the current service. Remember to re-enable them manually after the restore. -1. Check the values and click *Restore*. - -1. Navigate to the *Restore History* tab to check the status of the restored backup. +### Post-restore requirements for MongoDB +Restoring from a physical backup will cause all **mongo** and **pbm-agent** instances to shut down. To bring them back up: +1. Restart all **mongod** (and **mongos** if present) nodes. +2. Restart all **pbm-agents**. ## Delete a backup - -1. Select → *Backup* → *Backup Inventory*. - -1. Find the row with the backup you want to delete. - -1. In the *Actions* column for that row, click *Delete backup*. - -1. (Optional) Check *Delete from storage* to also delete the actual backup content besides just the backup register. - -1. Click *Delete* to proceed. - -[Amazon AWS S3]: https://aws.amazon.com/s3/ -[Percona Backup for MongoDB]: https://www.percona.com/doc/percona-backup-mongodb/installation.html -[PERCONA_QPRESS]: https://www.percona.com/doc/percona-xtrabackup/LATEST/backup_scenarios/compressed_backup.html -[PERCONA_XBCLOUD]: https://www.percona.com/doc/percona-xtrabackup/2.3/xbcloud/xbcloud.html -[PERCONA_XBSTREAM]: https://www.percona.com/doc/percona-xtrabackup/2.3/xbstream/xbstream.html -[PERCONA_XTRABACKUP]: https://www.percona.com/software/mysql-database/percona-xtrabackup -[Add a storage location]: #add-a-storage-location -[oplog slices]: https://www.percona.com/doc/percona-backup-mongodb/glossary.html#term-oplog-slice -[Percona Server for MongoDB]: https://www.percona.com/software/mongo-database/percona-server-for-mongodb -[MongoDB Replication]: https://docs.mongodb.com/manual/replication/ +You can only delete backup artifacts stored on Amazon S3. Local backups must be removed manually. + +To delete a backup: + +1. Go to **Backup > All Backups** and find the row with the backup you want to delete. +2. Click the arrow in the **Actions** column to check all the information for the backup, then click ![](../_images/dots-three-vertical.png) **> Delete backup**. +3. In the Delete backup artifact dialog box, enable **Delete from storage** if you also want to delete the actual backup content besides just the backup register. +4. Click **Delete**. + + +### Resources +- [Amazon AWS S3](https://aws.amazon.com/s3/) +- [Percona Backup for MongoDB](https://www.percona.com/doc/percona-backup-mongodb/installation.html) +- [PERCONA_QPRESS](https://www.percona.com/doc/percona-xtrabackup/LATEST/backup_scenarios/compressed_backup.html) +- [PERCONA_XBCLOUD](https://www.percona.com/doc/percona-xtrabackup/2.3/xbcloud/xbcloud.html) +- [PERCONA_XBSTREAM](https://www.percona.com/doc/percona-xtrabackup/2.3/xbstream/xbstream.html) +- [PERCONA_XTRABACKUP](https://www.percona.com/software/mysql-database/percona-xtrabackup) +- [oplog slices](https://www.percona.com/doc/percona-backup-mongodb/glossary.html#term-oplog-slice) +- [Percona Server for MongoDB](https://www.percona.com/software/mongo-database/percona-server-for-mongodb) +- [MongoDB Replication](https://docs.mongodb.com/manual/replication/) diff --git a/docs/using/mongodb_limitations.md b/docs/using/mongodb_limitations.md new file mode 100644 index 0000000000..1c57756c87 --- /dev/null +++ b/docs/using/mongodb_limitations.md @@ -0,0 +1,75 @@ +# MongoDB Backup and Restore support matrix + +Creating and restoring MongoDB backups in PMM currently has the following limitations and requirements: + +- Restoring on different Replica set/Cluster is not supported. +- Physical backups and restores suppoted only for **Percona Server for MongoDB** +- Physical restores are not supported for deployments with arbiter nodes. For more information, see the [Percona Backup for MongoDB documentation](https://docs.percona.com/percona-backup-mongodb/usage/restore.html#physical-restore-known-limitations). +- All types of backups on sharded cluster setups are currently not supported. +- Physical backups are supported, but restoring from physical backups will cause all mongo and pbm-agent instances to shutdown. To bring them back up, restart all **mongod** and **mongos** nodes and restart all **pbm-agents**. +- Retention policy is supported only for snapshot types of scheduled backups and for the S3 storage type. +- Before restoring, make sure to prevent clients from accessing database. + +## Support matrix + + + +| Operation (Backup or Restore) | Backup type (Logical or Physical) | Full or PITR | Storage type (S3 or Local) | Support DB running in container (Containerized) | Support level| +| -------------- | ---------------- | ---- | -------- | ------------- | --------------------------------------- | +| Backup | Logical | Yes | S3 | Yes | Full | | +| Backup | Logical | Yes | S3 | No | Full | | +| Backup | Logical | Yes | Local | Yes | Full +| Backup | Logical | Yes | Local | No | Full +| Backup | Logical | No | S3 | Yes | Full | | +| Backup | Logical | No | S3 | No | Full | | +| Backup | Logical | No | Local | Yes | Full +| Backup | Logical | No | Local | No | Full +| Backup | Physical | Yes | S3 | Yes | No +| Backup | Physical | Yes | S3 | No | No +| Backup | Physical | Yes | Local | Yes | No +| Backup | Physical | Yes | Local | No | No +| Backup | Physical | No | S3 | Yes | Full +| Backup | Physical | No | S3 | No | Full +| Backup | Physical | No | Local | Yes | Full +| Backup | Physical | No | Local | No | Full +| Restore | Logical | Yes | S3 | Yes | Full | | +| Restore | Logical | Yes | S3 | No | Full | | +| Restore | Logical | Yes | Local | Yes | No +| Restore | Logical | Yes | Local | No |No +| Restore | Logical | No | S3 | Yes | Full | | +| Restore | Logical | No | S3 | No | Full | | +| Restore | Logical | No | Local | Yes | Full | | +| Restore | Logical | No | Local | No | Full | | +| Restore | Physical | Yes | S3 | Yes | No +| Restore | Physical | Yes | S3 | No | No +| Restore | Physical | Yes | Local | Yes | No +| Restore | Physical | Yes | Local | No | No +| Restore | Physical | No | S3 | Yes | No +| Restore | Physical | No | S3 | No | Partial +| Restore | Physical | No | Local | Yes | No +| Restore | Physical | No | Local | No | Partial \ No newline at end of file diff --git a/mkdocs-base.yml b/mkdocs-base.yml index 2822a217d5..af7e10b9ac 100644 --- a/mkdocs-base.yml +++ b/mkdocs-base.yml @@ -71,7 +71,7 @@ plugins: with-pdf: output_path: "_pdf/PerconaMonitoringAndManagement-2.32.0.pdf" cover_title: "Documentation" - cover_subtitle: 2.32.0 (Nov 7, 2022) + cover_subtitle: 2.32.0 (Nov 8, 2022) author: "Percona Technical Documentation Team" cover_logo: docs/_images/PMM_Logo.svg custom_template_path: _resources/templates @@ -120,7 +120,9 @@ nav: - using/index.md - using/interface.md - using/alerting.md - - using/backup.md + - Backup and restore: + - using/backup.md + - using/mongodb_limitations.md - using/query-analytics.md - using/dbaas.md @@ -158,7 +160,6 @@ nav: - PMM dashboards: - Insight: - details/dashboards/dashboard-home.md - - details/dashboards/dashboard-home-experimental.md - details/dashboards/dashboard-advanced-data-exploration.md - details/dashboards/dashboard-victoriametrics.md - details/dashboards/dashboard-victoriametrics-agents-overview.md @@ -238,6 +239,7 @@ nav: - Release Notes: - release-notes/index.md + - "PMM 2.32.0": release-notes/2.32.0.md - "PMM 2.31.0": release-notes/2.31.0.md - "PMM 2.30.0": release-notes/2.30.0.md - "PMM 2.29.1": release-notes/2.29.1.md diff --git a/variables.yml b/variables.yml index c8775b7215..93fa55d1ee 100644 --- a/variables.yml +++ b/variables.yml @@ -1,9 +1,9 @@ # PMM Version for HTML # See also mkdocs.yml plugins.with-pdf.cover_subtitle and output_path -release: '2.31.0' -version: '2.31' -release_date: 2022-09-26 +release: '2.32.0' +version: '2.32' +release_date: 2022-11-08 # SVG icons. Use in markdown as {{icon.}} # For the Percona image icon (encoded inline SVG), see https://css-tricks.com/using-svg/