## :material-telescope: Discover { .title }
@@ -24,7 +22,6 @@ Discover how PMM can help you monitor your systems and make informed decisions.
[Discover PMM :material-arrow-right:](discover-pmm/features.md){ .md-button .md-button--primary }
-
## :material-progress-download: Install { .title }
diff --git a/documentation/docs/install-pmm/HA.md b/documentation/docs/install-pmm/HA.md
index 890d2a4ac8..c20fd81509 100644
--- a/documentation/docs/install-pmm/HA.md
+++ b/documentation/docs/install-pmm/HA.md
@@ -1,7 +1,7 @@
# Install PMM in HA mode
!!! caution alert alert-warning "Important"
- This feature is currently in [Technical Preview](https://docs.percona.com/percona-monitoring-and-management/details/glossary.html#technical-preview). Early adopters are advised to use this feature for testing purposes only as it is subject to change.
+ This feature is currently in [Technical Preview](../reference/glossary.md#technical-preview). Early adopters are advised to use this feature for testing purposes only as it is subject to change.
Set up PMM using Docker containers in a high-availability (HA) configuration following these instructions.
@@ -54,7 +54,7 @@ For all IP addresses, use the format `17.10.1.x`, and for all usernames and pass
| `PMM_PASSIVE_NODE_ID` | The unique ID for your first passive PMM Server node.Example: `pmm-server-passive`
| `PMM_PASSIVE2_IP` | The IP address of the instance where the second passive PMM Server is running or the desired IP address for your second passive PMM Server container within the Docker network, depending on your setup.Example: `17.10.1.7`
| `PMM_PASSIVE2_NODE_ID` | The unique ID for your second passive PMM Server node.Example: `pmm-server-passive2`
-| `PMM_DOCKER_IMAGE` | The specific PMM Server Docker image for this guide.Example: `perconalab/pmm-server:3.0.0-beta`
+| `PMM_DOCKER_IMAGE` | The specific PMM Server Docker image for this guide.Example: `percona/pmm-server:3`
??? example "Expected output"
@@ -73,7 +73,7 @@ For all IP addresses, use the format `17.10.1.x`, and for all usernames and pass
export PMM_PASSIVE_NODE_ID=pmm-server-passive
export PMM_PASSIVE2_IP=17.10.1.7
export PMM_PASSIVE2_NODE_ID=pmm-server-passive2
- export PMM_DOCKER_IMAGE=perconalab/pmm-server:3.0.0-beta
+ export PMM_DOCKER_IMAGE=percona/pmm-server:3
```
!!! note alert alert-primary "Note"
@@ -365,8 +365,8 @@ The PMM Server orchestrates the collection, storage, and visualization of metric
```sh
docker run -d \
--name ${PMM_ACTIVE_NODE_ID} \
- -p 80:80 \
- -p 443:443 \
+ -p 80:8080 \
+ -p 443:8443 \
-p 9094:9094 \
-p 9096:9096 \
-p 9094:9094/udp \
@@ -435,8 +435,8 @@ The PMM Server orchestrates the collection, storage, and visualization of metric
```sh
docker run -d \
--name ${PMM_PASSIVE_NODE_ID} \
- -p 80:80 \
- -p 443:443 \
+ -p 80:8080 \
+ -p 443:8443 \
-p 9094:9094 \
-p 9096:9096 \
-p 9094:9094/udp \
@@ -505,8 +505,8 @@ The PMM Server orchestrates the collection, storage, and visualization of metric
```sh
docker run -d \
--name ${PMM_PASSIVE2_NODE_ID} \
- -p 80:80 \
- -p 443:443 \
+ -p 80:8080 \
+ -p 443:8443 \
-p 9094:9094 \
-p 9096:9096 \
-p 9094:9094/udp \
@@ -545,11 +545,10 @@ The PMM Server orchestrates the collection, storage, and visualization of metric
### **Step 7: Running HAProxy**
-HAProxy provides high availability for your PMM setup by directing traffic to the current leader server via the `/v1/leaderHealthCheck` endpoint.
-
+HAProxy provides high availability for your PMM setup by directing traffic to the current leader server via the `/v1/leaderHealthCheck` endpoint:
+{.power-number}
-1. Pull the HAProxy Docker image.
-{.power-number}
+1. Pull the HAProxy Docker image:
```bash
docker pull haproxy:2.4.2-alpine
diff --git a/documentation/docs/install-pmm/index.md b/documentation/docs/install-pmm/index.md
index 03e56a7e0b..36737cba65 100644
--- a/documentation/docs/install-pmm/index.md
+++ b/documentation/docs/install-pmm/index.md
@@ -17,11 +17,11 @@ Install and run at least one PMM Server. Choose from the following options:
| Use | :material-thumb-up: **Benefits** | :material-thumb-down: **Drawbacks**|
|---|---|---
-| [Docker] | 1. Quick
2. Simple
3. Rootless | Additional network configuration required.
-| [Podman] | 1. Quick
2. Simple
3. Rootless | Podman installation required.
-| [Helm] (Technical Preview) | 1. Quick
2. Simple
3. Cloud-compatible
4. Rootless| Requires running a Kubernetes cluster.
-| [Virtual appliance] | 1. Easily import into Hypervisor of your choice
2. Rootless| More system resources compared to Docker footprint.
-| [Amazon AWS] | 1. Wizard-driven install.
2. Rootless| Paid, incurs infrastructure costs.
+| [Docker](../install-pmm/install-pmm-server/deployment-options/docker/index.md) | 1. Quick
2. Simple
3. Rootless | Additional network configuration required.
+| [Podman](../install-pmm/install-pmm-server/deployment-options/podman/index.md) | 1. Quick
2. Simple
3. Rootless | Podman installation required.
+| [Helm](../install-pmm/install-pmm-server/deployment-options/helm/index.md) (Technical Preview) | 1. Quick
2. Simple
3. Cloud-compatible
4. Rootless| Requires running a Kubernetes cluster.
+| [Virtual appliance](../install-pmm/install-pmm-server/deployment-options/virtual/index.md) | 1. Easily import into Hypervisor of your choice
2. Rootless| More system resources compared to Docker footprint.
+| [Amazon AWS](../install-pmm/install-pmm-server/deployment-options/aws/aws.md) | 1. Wizard-driven install.
2. Rootless| Paid, incurs infrastructure costs.
## Install PMM Client
@@ -31,15 +31,15 @@ The installation choices are:
=== "With Docker"
- - [Docker installation](client/index.md#docker) simplifies deployment across different architectures and automatically selects the appropriate image for your architecture (x86_64 or ARM64).
+ [Running PMM Client as a Docker container](../install-pmm/install-pmm-client/docker.md) simplifies deployment across different architectures and automatically selects the appropriate image for your architecture (x86_64 or ARM64).
=== "With package manager"
- - [Linux package](client/index.md#package-manager). Use `apt`, `apt-get`, `dnf`, `yum`. The package manager automatically selects the correct version for your architecture.
+ [Linux package](../install-pmm/install-pmm-client/package_manager.md): Use `apt`, `apt-get`, `dnf`, `yum`. The package manager automatically selects the correct version for your architecture.
=== "With binary package"
- - [Binary package](client/index.md#binary-package): Download the appropriate `.tar.gz` file for your architecture (x86_64 or ARM64).
+ [Binary package](../install-pmm/install-pmm-client/binary_package.md): Download the appropriate `.tar.gz` file for your architecture (x86_64 or ARM64).
!!! hint alert "Tips"
@@ -51,33 +51,14 @@ On each PMM Client instance, configure the nodes and services you want to monito
??? info "Which services you can monitor?"
- - [MySQL] (and variants: Percona Server for MySQL, Percona XtraDB Cluster, MariaDB);
- - [MongoDB];
- - [PostgreSQL];
- - [ProxySQL];
- - [Amazon RDS];
- - [Microsoft Azure];
- - [Google Cloud Platform] (MySQL and PostgreSQL);
- - [Linux];
- - [External services];
- - [HAProxy];
- - [Remote instances].
-
-[MySQL]: client/mysql.md
-[MongoDB]: client/mongodb.md
-[PostgreSQL]: client/postgresql.md
-[ProxySQL]: client/proxysql.md
-[Amazon RDS]: client/aws.md
-[Microsoft Azure]: client/azure.md
-[Google Cloud Platform]: client/google.md
-[Linux]: client/linux.md
-[External services]: client/external.md
-[HAProxy]: client/haproxy.md
-[Remote instances]: client/remote.md
-[dashboards]: ../details/dashboards/
-[Docker]: ../install-pmm/install-pmm-server/baremetal/docker/index.md
-[Podman]: ../install-pmm/install-pmm-server/baremetal/podman/index.md
-[Helm]: ../install-pmm/install-pmm-server/baremetal/helm/index.md
-[virtual appliance]: ../install-pmm/install-pmm-server/baremetal/virtual/index.md
-[Amazon AWS]: ../install-pmm/install-pmm-server/aws/aws.md
-[easy install]: ../install-pmm/install-pmm-server/baremetal/easy-install.md
+ - [MySQL](../install-pmm/install-pmm-client/connect-database/mysql.md) and variants: Percona Server for MySQL, Percona XtraDB Cluster, MariaDB
+ - [MongoDB](../install-pmm/install-pmm-client/connect-database/mongodb.md)
+ - [PostgreSQL](../install-pmm/install-pmm-client/connect-database/postgresql.md)
+ - [ProxySQL](../install-pmm/install-pmm-client/connect-database/proxysql.md)
+ - [Amazon RDS](../install-pmm/install-pmm-client/connect-database/aws.md)
+ - [Microsoft Azure](../install-pmm/install-pmm-client/connect-database/azure.md)
+ - [Google Cloud Platform](../install-pmm/install-pmm-client/connect-database/google.md)
+ - [Linux](../install-pmm/install-pmm-client/connect-database/linux.md)
+ - [External services](../install-pmm/install-pmm-client/connect-database/external.md)
+ - [HAProxy](../install-pmm/install-pmm-client/connect-database/haproxy.md)
+ - [Remote instances](../install-pmm/install-pmm-client/connect-database/remote.md)
diff --git a/documentation/docs/install-pmm/install-pmm-client/binary_package.md b/documentation/docs/install-pmm/install-pmm-client/binary_package.md
index a0fb011694..df706d40a1 100644
--- a/documentation/docs/install-pmm/install-pmm-client/binary_package.md
+++ b/documentation/docs/install-pmm/install-pmm-client/binary_package.md
@@ -10,24 +10,24 @@ Choose your installation instructions based on whether you have root permissions
=== "For x86_64 (AMD64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz
```
=== "For ARM64 (aarch64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz
```
2. Download the corresponding checksum file:
=== "For x86_64 (AMD64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz.sha256sum
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz.sha256sum
```
=== "For ARM64 (aarch64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz.sha256sum
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz.sha256sum
```
3. Verify the download:
@@ -99,24 +99,24 @@ Choose your installation instructions based on whether you have root permissions
=== "For x86_64 (AMD64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz
```
=== "For ARM64 (aarch64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz
```
2. Download the corresponding checksum file:
=== "For x86_64 (AMD64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz.sha256sum
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-x86_64.tar.gz.sha256sum
```
=== "For ARM64 (aarch64)"
```sh
- wget https://downloads.percona.com/downloads/pmm/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz.sha256sum
+ wget https://downloads.percona.com/downloads/pmm3/{{release}}/binary/tarball/pmm-client-{{release}}-aarch64.tar.gz.sha256sum
```
3. Verify the download:
@@ -186,4 +186,4 @@ Choose your installation instructions based on whether you have root permissions
- Extract it.
- Run `./install_tarball script `with the `-u` flag.
-The configuration file will be overwritten if you do not provide the -`u` flag while the pmm-agent is updated.
\ No newline at end of file
+The configuration file will be overwritten if you do not provide the -`u` flag while the pmm-agent is updated.
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/aws.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/aws.md
index ed119c1d76..04be4228bd 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/aws.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/aws.md
@@ -153,7 +153,7 @@ GRANT SELECT, UPDATE, DELETE, DROP ON performance_schema.* TO 'pmm'@'%';
It may take longer for PMM to discover Amazon RDS instances in the `creating` state. You must wait a bit longer until PMM discovers these instances.
-The preferred method of adding an Amazon RDS database instance to PMM is via the
**Configuration** → {{icon.inventory}} **PMM Inventory** → {{icon.addinstance}} **Add Instance** menu option.
+The preferred method of adding an Amazon RDS database instance to PMM is via the :material-cog: **PMM Configuration > PMM Inventory > Add Instance** menu option.
This method supports Amazon RDS database instances that use Amazon Aurora, MySQL, or MariaDB engines, as well as any remote PostgreSQL, ProxySQL, MySQL and MongoDB instances.
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/external.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/external.md
index f4ebb44055..2c2403c037 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/external.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/external.md
@@ -29,11 +29,11 @@ Here are the differences between `external` and `external-serverless` types.
Connection schema of external exporter:
-
+
Connection schema of external serverless exporter:
-
+
## Add a service not supported by PMM
@@ -43,7 +43,7 @@ From this point, PMM will collect and store available metrics.
To browse and visualize collected metrics as a first step, we can look at the Advanced Data Exploration dashboard and select informative services and metrics.
-
+
Another way is to create a [new Grafana Dashboard to PMM as needed](https://grafana.com/docs/grafana/latest/best-practices/best-practices-for-creating-dashboards/).
@@ -80,14 +80,14 @@ To add an external service via PMM UI:
1. In the PMM web interface, go to **PMM Configuration > PMM Inventory > Add Service > External Service**.
- 
+ 
2. Fill in the form and set the external service endpoint:
- - manually OR:
+ - manually OR:
- 
+ 
-- by parsing required data from a URL string. In this case you only need to pass a valid URL:
+ - by parsing required data from a URL string. In this case you only need to pass a valid URL:
- 
+ 
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/google.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/google.md
index cb76639f85..5c87ee2a88 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/google.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/google.md
@@ -49,8 +49,6 @@ To add a PostgreSQL instance on Google Cloud:
6. Fill in the details for the remote PostgreSQL instance and make sure to **PG Stat Statements** option under **Stat tracking options**.
- 
-
7. Click **Add service**.
8. Go to **Dashboards** and check for values in the **PostgreSQL Instances Overview** and **Query Analytics**.
@@ -93,7 +91,7 @@ To add a MySQL instance:
-credential_file=/path/to/credential-file.json
```
-6. Add instance.
+6. Add instance:
```sh
pmm-admin add mysql --host=127.0.0.1 --port=3306 \
@@ -112,7 +110,7 @@ To add a PostgreSQL instance:
3. [Enable Admin API][GOOGLE_CLOUD_ADMIN_API] and download the JSON credential file.
-4. Run Cloud SQL Proxy.
+4. Run Cloud SQL Proxy:
```sh
./cloud_sql_proxy -instances=example-project-NNNN:us-central1:pg-for-pmm=tcp:5432 \
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/index.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/index.md
index 2b5877f79d..51369934ef 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/index.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/index.md
@@ -8,7 +8,7 @@ You must configure and add database/service according to the service type.
- [ProxySQL](proxysql.md)
- [Amazon RDS](aws.md)
- [Microsoft Azure](azure.md)
-- [Google Cloud Platform](google) (MySQL and PostgreSQL)
+- [Google Cloud Platform](google.md) (MySQL and PostgreSQL)
- [Linux](linux.md)
- [External services](external.md)
- [HAProxy](haproxy.md)
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/mongodb.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/mongodb.md
index 840ee009fb..de15f4bae9 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/mongodb.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/mongodb.md
@@ -88,7 +88,7 @@ Create or update a user with the minimum required privileges for monitoring by a
"roles": [
{ "db": "admin", "role": "explainRole" },
{ "db": "local", "role": "read" },
- { "db": "admin". "role": "clusterMonitor" }
+ { "db": "admin", "role": "clusterMonitor" }
]
})
```
@@ -202,7 +202,7 @@ Use `pmm-admin` to add the database server as a service using one of these examp
When successful, PMM Client will print `MongoDB Service added` with the service's ID and name. Use the `--environment` and `-custom-labels` options to set tags for the service to help identify them.
!!! hint alert alert-success "Tips"
- - When adding nodes to a sharded cluster, ensure to add each node separately using the `--cluster mycluster` option. This allows the [MongoDB Cluster Summary](../../details/dashboards/dashboard-mongodb-cluster-summary.md) dashboard to populate correctly.
+ - When adding nodes to a sharded cluster, ensure to add each node separately using the `--cluster mycluster` option. This allows the [MongoDB Cluster Summary](../../../reference/dashboards/dashboard-mongodb-cluster-summary.md) dashboard to populate correctly.
- You can also use the `--replication-set` option to specify a replication set, altough they are automatically detected. For instance, you can use `--replication-set config` for your config servers; `--replication-set rs1` for your servers in the first replica set, `--replication-set rs2` for your servers in the second replica set, and so on.
- When running mongos routers in containers, specify the `diagnosticDataCollectionDirectoryPath` to ensure that pmm-agent can properly capture mongos metrics. For example: `mongos --setParameter diagnosticDataCollectionDirectoryPath=/var/log/mongo/mongos.diagnostic.data/`
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/mysql.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/mysql.md
index f0fe7f39ac..fd32a47b07 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/mysql.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/mysql.md
@@ -27,19 +27,28 @@ Check that:
## Create a database account for PMM
-It is good practice to use a non-superuser account to connect PMM Client to the monitored database instance. This example creates a database user with name `pmm`, password `pass`, and the necessary permissions.
+For security, connect PMM Client to your database using a dedicated monitoring user with limited permissions. This example creates a pmm user account that has just enough access to collect monitoring data without full administrative privileges.
+
+!!! warning "Password security"
+ - Use a strong, unique password for the PMM database user
+ - At least 12 characters long
+ - Mix of uppercase and lowercase letters
+ - Include numbers and special characters
+ - Avoid common words or patterns
+ - Never use default, test, or example passwords in production
+
=== "On MySQL 5.7"
```sql
- CREATE USER 'pmm'@'127.0.0.1' IDENTIFIED BY 'pass' WITH MAX_USER_CONNECTIONS 10;
+ CREATE USER 'pmm'@'127.0.0.1' IDENTIFIED BY '
' WITH MAX_USER_CONNECTIONS 10;
GRANT SELECT, PROCESS, REPLICATION CLIENT, RELOAD ON *.* TO 'pmm'@'localhost';
```
=== "On MySQL 8.0"
```sql
- CREATE USER 'pmm'@'localhost' IDENTIFIED BY 'pass' WITH MAX_USER_CONNECTIONS 10;
+ CREATE USER 'pmm'@'localhost' IDENTIFIED BY '' WITH MAX_USER_CONNECTIONS 10;
GRANT SELECT, PROCESS, REPLICATION CLIENT, RELOAD, BACKUP_ADMIN ON *.* TO 'pmm'@'localhost';
```
@@ -93,7 +102,7 @@ The *slow query log* records the details of queries that take more than a certai
??? info "Examples"
- - Configuration file.
+ - Configuration file:
```ini
slow_query_log=ON
@@ -103,7 +112,7 @@ The *slow query log* records the details of queries that take more than a certai
log_slow_slave_statements=ON
```
- - Session.
+ - Session:
```sql
SET GLOBAL slow_query_log = 1;
@@ -137,7 +146,7 @@ Some MySQL-based database servers support extended slow query log variables.
??? info "Examples"
- - Configuration file (Percona Server for MySQL, Percona XtraDB Cluster).
+ - Configuration file (Percona Server for MySQL, Percona XtraDB Cluster):
```sh
log_slow_rate_limit=100
@@ -147,13 +156,13 @@ Some MySQL-based database servers support extended slow query log variables.
slow_query_log_use_global_control='all'
```
- - Configuration file (MariaDB).
+ - Configuration file (MariaDB):
```sh
log_slow_rate_limit=100
```
- - Session (Percona Server for MySQL, Percona XtraDB Cluster).
+ - Session (Percona Server for MySQL, Percona XtraDB Cluster):
```sh
SET GLOBAL log_slow_rate_limit = 100;
@@ -167,7 +176,7 @@ Some MySQL-based database servers support extended slow query log variables.
Slow query log files can grow quickly and must be managed.
-When adding a service with the command line use the `pmm-admin` option `--size-slow-logs` to set at what size the slow query log file is rotated. (The size is specified as a number with a suffix. See [`pmm-admin add mysql`](../../details/commands/pmm-admin.md#mysql).)
+When adding a service with the command line use the `pmm-admin` option `--size-slow-logs` to set at what size the slow query log file is rotated. (The size is specified as a number with a suffix. See [`pmm-admin add mysql`](../../../use/commands/pmm-admin.md#mysql).)
When the limit is reached, PMM Client will:
@@ -191,9 +200,9 @@ This section covers how to configure a MySQL-based database server to use *Perfo
| Percona XtraDB Cluster | 5.6, 5.7, 8.0
| MariaDB | [10.3+][mariadb_perfschema_instr_table]
-PMM's [*MySQL Performance Schema Details* dashboard](../../../use/dashboards/dashboard-mysql-performance-schema-details.md) charts the various [`performance_schema`][performance-schema-startup-configuration] metrics.
+PMM's [*MySQL Performance Schema Details* dashboard](../../../reference/dashboards/dashboard-mysql-performance-schema-details.md) charts the various [`performance_schema`][performance-schema-startup-configuration] metrics.
-To use *Performance Schema*, set these variables.
+To use **Performance Schema**, set these variables:
| Variable | Value | Description
|--------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------------------------
@@ -204,7 +213,7 @@ To use *Performance Schema*, set these variables.
??? info "Examples"
- - Configuration file.
+ - Configuration file:
```ini
performance_schema=ON
@@ -213,7 +222,7 @@ To use *Performance Schema*, set these variables.
innodb_monitor_enable=all
```
- - Session.
+ - Session:
(`performance_schema` cannot be set in a session and must be set at server start-up.)
@@ -267,7 +276,7 @@ Set this variable to see query time distribution charts.
|-------------------------------------------------------------|-------|-----------------------------------------------------------------------------------
| [`query_response_time_stats`][ps_query_response_time_stats] | ON | Report *query response time distributions*. (Requires plugin installation. See below.)
-- Configuration file.
+- Configuration file:
```ini
query_response_time_stats=ON
@@ -276,6 +285,8 @@ Set this variable to see query time distribution charts.
You must also install the plugins.
- **Session**
+ Before installing the plugins, ensure you have the necessary plugin files and run these commands in your MySQL session:
+ {.power-number}
1. Check that `/usr/lib/mysql/plugin/query_response_time.so` exists.
2. Install the plugins and activate.
@@ -338,15 +349,17 @@ User activity, individual table and index access details are shown on the [MySQL
## Add service
There are two ways to install PMM Client for monitoring your MySQL database:
+{.power-number}
-1. [Local installation](#Install-PMM-Client locally): Installs PMM Client directly on the database node, collecting both database and OS/host metrics. This option enables more effective comparison and problem identification.
-2. [Remote instance](#Install-PMM-Client-as-a-remote-instance): Use when local installation isn't possible. This method doesn't provide OS/Node metrics in PMM.
+1. [Local installation](#install-pmm-client-locally): Installs PMM Client directly on the database node, collecting both database and OS/host metrics. This option enables more effective comparison and problem identification.
+2. [Remote instance](#install-pmm-client-as-a-remote-instance): Use when local installation isn't possible. This method doesn't provide OS/Node metrics in PMM.
### Install PMM Client locally
Add the MySQL server as a service using one of the following example commands.
Upon successful addition, PMM Client will display "MySQL Service added" along with the service's ID and name.
+{.power-number}
1. Select **PMM Configuration > PMM Inventory > Add Service > MySQL**.
@@ -354,9 +367,9 @@ Upon successful addition, PMM Client will display "MySQL Service added" along wi
3. Click **Add service**.
-
+ 
-If your MySQL instance is configured to use TLS, click on the *Use TLS for database connections* check box and fill in your TLS certificates and key.
+If your MySQL instance is configured to use TLS, click on the **Use TLS for database connections*** check box and fill in your TLS certificates and key:
@@ -364,17 +377,18 @@ If your MySQL instance is configured to use TLS, click on the *Use TLS for datab
Add the database server as a service using one of these example commands. If successful, PMM Client will print `MySQL Service added` with the service's ID and name. Use the `--environment` and `-custom-labels` options to set tags for the service to help identify them.
-??? info "Examples"
#### TLS connection
```sh
-pmm-admin add mysql --environment=test --custom-labels='source=slowlog' --username=root --password=password --query-source=slowlog MySQLSlowLog localhost:3306
+pmm-admin add mysql --environment=test --custom-labels='source=slowlog' --username=root --password=password --tls --tls-skip-verify --tls-ca=pathtoca.pem --tls-cert=pathtocert.pem --tls-key=pathtocertkey.pem --query-source=slowlog MySQLSlowLog localhost:3306
```
### Install PMM Client as a remote instance
+If you need to monitor a MySQL instance from a different server where PMM Client is installed, follow these steps in the PMM web interface:
+{.power-number}
-1. Select ** PMM Configuration > PMM Inventory > {{icon.addinstance}} Add Service**.
+1. Select :material-cog: **PMM Configuration > PMM Inventory > :material-plus-circle-outline: Add Service**.
2. Choose **MySQL > Add a remote instance**.
@@ -382,16 +396,17 @@ pmm-admin add mysql --environment=test --custom-labels='source=slowlog' --usern
4. Click **Add service**.
-
+ 
#### For MySQL instances using TLS
If your MySQL instance is configured to use TLS:
+{.power-number}
1. Click on the **Use TLS for database connections** check box.
2. Fill in your TLS certificates and key.
-
+ 
## Check the service
@@ -442,8 +457,8 @@ Open the [*PXC/Galera Cluster Summary* dashboard][DASH_PXCGALERACLUSTER].
- [Percona Blog -- Impact of logging on MySQL's performance][BLOG_LOGGING]
- [Percona Blog -- Running Custom MySQL Queries in Percona Monitoring and Management][BLOG_CUSTOM_QUERIES_MYSQL]
-[DASH_MYSQLUSERDETAILS]: ../../../use/dashboards/dashboard-mysql-user-details.md
-[DASH_PXCGALERACLUSTER]: ../../../use/dashboards/dashboard-pxc-galera-cluster-summary.md
+[DASH_MYSQLUSERDETAILS]: ../../../reference/dashboards/dashboard-mysql-user-details.md
+[DASH_PXCGALERACLUSTER]: ../../../reference/dashboards/dashboard-pxc-galera-cluster-summary.md
[LOGROTATE]: https://linux.die.net/man/8/logrotate
[PERCONA_SERVER_MYSQL]: https://www.percona.com/software/mysql-database/percona-server
[PERCONA_XTRADB_CLUSTER]: https://www.percona.com/software/mysql-database/percona-xtradb-cluster
@@ -455,19 +470,19 @@ Open the [*PXC/Galera Cluster Summary* dashboard][DASH_PXCGALERACLUSTER].
[BLOG_LOG_ROTATION]: https://www.percona.com/blog/2013/04/18/rotating-mysql-slow-logs-safely/
[BLOG_PS_VS_SLOW]: https://www.percona.com/blog/2014/02/11/performance_schema-vs-slow-query-log/
[PS_FEATURES_REMOVED]: https://www.percona.com/doc/percona-server/LATEST/changed_in_version.html
-[ps_slow_query_ext]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/slow_extended.html
+[ps_slow_query_ext]: https://docs.percona.com/percona-server/latest/slow-extended.html
[ps_query_response_time_stats]: https://www.percona.com/doc/percona-server/5.7/diagnostics/response_time_distribution.html#usage
-[ps_userstats]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/user_stats.html
+[ps_userstats]: https://docs.percona.com/percona-server/latest/user-stats.html
[mariadb_slow_query_log]: https://mariadb.com/kb/en/slow-query-log-overview/
[mariadb_slow_query_ext]: https://mariadb.com/kb/en/slow-query-log-extended-statistics/
[mariadb_query_response_time]: https://mariadb.com/kb/en/query-response-time-plugin/
[mariadb_perfschema_instr_table]: https://mariadb.com/kb/en/performance-schema-setup_instruments-table/
[mariadb_userstats]: https://mariadb.com/kb/en/user-statistics/
-[log_slow_rate_limit]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/slow_extended.html#log_slow_rate_limit
-[log_slow_rate_type]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/slow_extended.html#log_slow_rate_type
-[log_slow_verbosity]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/slow_extended.html#log_slow_verbosity
-[slow_query_log_always_write_time]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/slow_extended.html#slow_query_log_always_write_time
-[slow_query_log_use_global_control]: https://www.percona.com/doc/percona-server/LATEST/diagnostics/slow_extended.html#slow_query_log_use_global_control
+[log_slow_rate_limit]: https://www.percona.com/doc/percona-server/LATEST/slow-extended.html?h=log_slow_rate_limit#log_slow_rate_limit
+[log_slow_rate_type]: https://docs.percona.com/percona-server/latest/slow-extended.html?h=log_slow_rate_limit#log_slow_rate_limit
+[log_slow_verbosity]: https://docs.percona.com/percona-server/latest/slow-extended.html?h=log_slow_rate_limit#log_slow_verbosity
+[slow_query_log_always_write_time]: https://docs.percona.com/percona-server/latest/slow-extended.html?h=log_slow_rate_limit#slow_query_log_always_write_time
+[slow_query_log_use_global_control]: https://docs.percona.com/percona-server/latest/slow-extended.html?h=log_slow_rate_limit#slow_query_log_use_global_control
[sysvar_innodb_monitor_enable]: https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_monitor_enable
[sysvar_log_output]: https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_output
[sysvar_log_slow_admin_statements]: https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_slow_admin_statements
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/postgresql.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/postgresql.md
index fa2f8743c2..a9c4dcc7dc 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/postgresql.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/postgresql.md
@@ -88,7 +88,7 @@ Here are the benefits and drawbacks of each.
| `pg_stat_statements` | 1. Part of official `postgresql-contrib` package. | 1. No aggregated statistics or histograms.
2. No Query Examples.
| `pg_stat_monitor` | 1. Builds on `pg_stat_monitor` features.
2. Bucket-based aggregation. |
-For a more detailed comparison of extensions, follow [pg_stat monitor User Guide](https://github.com/percona/pg_stat_monitor/blob/master/docs/USER_GUIDE.md#usage)
+For a more detailed comparison of extensions, follow [pg_stat monitor User Guide](https://docs.percona.com/pg-stat-monitor/user_guide.html)
!!! note alert alert-primary "Bucket-based data aggregation"
`pg_stat_monitor` collects statistics and aggregates data in a data collection unit called a *bucket*. These are linked together to form a *bucket chain*.
@@ -126,6 +126,7 @@ For a more detailed comparison of extensions, follow [pg_stat monitor User Guide
#### Configure
To configure the extension:
+{.power-number}
1. Add these lines to your `postgresql.conf` file:
@@ -373,7 +374,7 @@ The `pmm-admin` flag limits Auto-discovery:
To check the service from the PMM UI:
{.power-number}
-1. Select **Configuration** → {{icon.inventory}} **Inventory**.
+1. Select :material-cog: **Configuration** → :material-clipboard-list-outline: **Inventory**.
2. In the **Services** tab, verify the **Service name**, **Address** and any other relevant details.
3. In the **Options** column, expand the **Details** section and check that the Agents are using the desired data source.
diff --git a/documentation/docs/install-pmm/install-pmm-client/connect-database/remove-services/index.md b/documentation/docs/install-pmm/install-pmm-client/connect-database/remove-services/index.md
index e414c53f66..ce326bfb76 100644
--- a/documentation/docs/install-pmm/install-pmm-client/connect-database/remove-services/index.md
+++ b/documentation/docs/install-pmm/install-pmm-client/connect-database/remove-services/index.md
@@ -11,4 +11,4 @@ pmm-admin remove
!!! seealso alert alert-info "See also"
- [Percona release](https://www.percona.com/doc/percona-repo-config/percona-release.html)
- - [PMM Client architecture](../../../../reference/index.md#pmm-client_1)
+ - [PMM Client architecture](../../../../reference/index.md#pmm-client1)
diff --git a/documentation/docs/install-pmm/install-pmm-client/docker.md b/documentation/docs/install-pmm/install-pmm-client/docker.md
index e571c51349..f219803f12 100644
--- a/documentation/docs/install-pmm/install-pmm-client/docker.md
+++ b/documentation/docs/install-pmm/install-pmm-client/docker.md
@@ -1,4 +1,4 @@
-# Run PMM client as a Docker container
+# Run PMM Client as a Docker container
The [PMM Client Docker image](https://hub.docker.com/r/percona/pmm-client/tags/) is a convenient way to run PMM Client as a preconfigured [Docker](https://docs.docker.com/get-docker/) container.
@@ -8,58 +8,58 @@ The PMM Client Docker image is available for both x86_64 and ARM64 architectures
1. Pull the PMM Client Docker image:
```sh
- docker pull \
- percona/pmm-client:2
+ docker pull percona/pmm-client:3
```
-2. Use the image as a template to create a persistent data store that preserves local data when the image is updated:
+2. Create a Docker volume to store persistent data:
++ ```sh
++ docker volume create pmm-client-data
++ ```
- ```sh
- docker create \
- --volume /srv \
- --name pmm-client-data \
- percona/pmm-client:2 /bin/true
- ```
-
-3. Run the container to start [pmm-agent](../../use/commands/pmm-agent.md) in setup mode. Set `X.X.X.X` to the IP address of your PMM Server. (Do not use the `docker --detach` option as PMM agent only logs to the console.)
+3. Execute the following command to start the [pmm-agent](../../use/commands/pmm-agent.md) in Setup mode. Replace `X.X.X.X` with the IP address of your PMM Server:
```sh
- PMM_SERVER=X.X.X.X:443
- docker run \
- --rm \
- --name pmm-client \
- -e PMM_AGENT_SERVER_ADDRESS=${PMM_SERVER} \
- -e PMM_AGENT_SERVER_USERNAME=admin \
- -e PMM_AGENT_SERVER_PASSWORD=admin \
- -e PMM_AGENT_SERVER_INSECURE_TLS=1 \
- -e PMM_AGENT_SETUP=1 \
- -e PMM_AGENT_CONFIG_FILE=config/pmm-agent.yaml \
- --volumes-from pmm-client-data \
- percona/pmm-client:2
+ PMM_SERVER=X.X.X.X:443
+ docker run \
+ --rm \
+ --name pmm-client \
+ -e PMM_AGENT_SERVER_ADDRESS=${PMM_SERVER} \
+ -e PMM_AGENT_SERVER_USERNAME=admin \
+ -e PMM_AGENT_SERVER_PASSWORD=admin \
+ -e PMM_AGENT_SERVER_INSECURE_TLS=1 \
+ -e PMM_AGENT_SETUP=1 \
+ -e PMM_AGENT_CONFIG_FILE=config/pmm-agent.yaml \
+ -v pmm-client-data:/srv \
+ percona/pmm-client:3
```
-!!! hint alert-success "Tips"
- You can find a complete list of compatible environment variables [here](../../use/commands/pmm-agent.md).
+ !!! hint alert-success "Important"
+ - Do not use the `docker --detach` option with Docker, as the pmm-agent logs output directly to the console, and detaching the container will prevent you from seeing these logs:
+ - You can find a complete list of compatible environment variables [here](../../use/commands/pmm-agent.md).
-3. Check status.
+3. Check status:
```sh
- docker exec pmm-client \
- pmm-admin status
+ docker exec -t pmm-client pmm-admin status
```
In the PMM user interface you will also see an increase in the number of monitored nodes.
You can now add services with [`pmm-admin`](../../use/commands/pmm-admin.md) by prefixing commands with `docker exec pmm-client`.
-!!! hint alert alert-success "Tips"
- - Adjust host firewall and routing rules to allow Docker communications. ([Read more](../../troubleshoot/checklist.md)
- - For help: `docker run --rm percona/pmm-client:2 --help`
+!!! hint alert alert-success "Tips for Docker configuration"
+
+ - Firewall and routing rules: Ensure your host's firewall and routing rules are configured to allow Docker communications. This is crucial for Docker containers to communicate properly. For more details, see to the [troubleshooting checklist](https://chat.deepseek.com/a/troubleshoot/checklist.md).
+
+ - Help command: If you need assistance with PMM Client, you can run the following command to display help information: `docker run --rm percona/pmm-client:3 --help`.
+
+How to view your monitored node
+{.power-number}
+
+ 1. Go to the main menu and select **Operating System (OS) > Overview**.
- In the GUI:
+ 2. In the **Node Names** drop-down menu, select the node you recently registered.
- - Select {{icon.dashboards}} *PMM Dashboards* → {{icon.node}} *System (Node)* → {{icon.node}} *Node Overview*.
- - In the *Node Names* menu, select the new node.
- - Change the time range to see data.
+ 3. Modify the time range to view the relevant data for your selected node.
!!! danger alert alert-danger "Danger"
`pmm-agent.yaml` contains sensitive credentials and should not be shared.
diff --git a/documentation/docs/install-pmm/install-pmm-client/index.md b/documentation/docs/install-pmm/install-pmm-client/index.md
index 6d61e7b8a1..cf0c11dc50 100644
--- a/documentation/docs/install-pmm/install-pmm-client/index.md
+++ b/documentation/docs/install-pmm/install-pmm-client/index.md
@@ -1,4 +1,4 @@
-# About PMM client installation
+# About PMM Client installation
There are different ways to install PMM Client on a node and register it with PMM Server. Choose from:
@@ -16,7 +16,7 @@ When you have installed PMM Client, you must:
- [Register the node with PMM Server](../register-client-node/index.md).
- [Configure and add services according to type](connect-database/index.md).
-If you need to, you can [unregister](../../uninstall-pmm/unregister_client.md), [remove services](..//..//uninstall-pmm/remove_services.md) or [remove PMM Client](..//..//uninstall-pmm/uninstall_docker.md).
+If you need to, you can [unregister](../../uninstall-pmm/unregister_client.md), [remove services](../install-pmm-client/connect-database/remove-services/index.md) or [remove PMM Client](../../uninstall-pmm/uninstall_docker.md).
---
diff --git a/documentation/docs/install-pmm/install-pmm-client/package_manager.md b/documentation/docs/install-pmm/install-pmm-client/package_manager.md
index 6e8fcb1eb4..a72f9c7a09 100644
--- a/documentation/docs/install-pmm/install-pmm-client/package_manager.md
+++ b/documentation/docs/install-pmm/install-pmm-client/package_manager.md
@@ -1,102 +1,93 @@
-# Install PMM client with Percona repositories
-
+# Install PMM Client with Percona repositories
PMM Client supports both x86_64 and ARM64 architectures.
+
On Debian or Red Hat Linux, install `percona-release` and use a Linux package manager (`apt`/`dnf`) to install PMM Client.
The package manager will automatically select the appropriate version for your system architecture.
!!! hint alert alert-success "Tip"
If you have used `percona-release` before, disable and re-enable the repository:
-
```sh
percona-release disable all
- percona-release percona-release enable pmm3-client
+ percona-release enable pmm3-client
```
=== "Debian-based"
- To install PMM client:
+ To install PMM Client:
{.power-number}
- 1. Configure repositories.
-
+ 1. Configure repositories:
```sh
wget https://repo.percona.com/apt/percona-release_latest.generic_all.deb
dpkg -i percona-release_latest.generic_all.deb
```
-
- 2. Install the PMM Client package.
-
+ 2. Enable pmm3-client repository:
+ ```sh
+ percona-release enable pmm3-client
+ ```
+ 3. Install the PMM Client package:
!!! hint "Root permissions"
```sh
apt update
apt install -y pmm-client
```
-
- 3. Check.
-
+ 4. Verify the installation by checking the PMM Client version:
```sh
pmm-admin --version
```
-
- 4. [Register the node](..//register-client-node/index.md).
+ 5. [Register the node](..//register-client-node/index.md).
=== "Red Hat-based"
+ To install PMM Client:
+ {.power-number}
- 1. Configure repositories.
-
+ 1. Configure repositories:
```sh
yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
```
-
- 2. Install the PMM Client package.
-
+ 2. Enable pmm3-client repository:
+ ```sh
+ percona-release enable pmm3-client
+ ```
+ 3. Install the PMM Client package:
```sh
yum install -y pmm-client
```
-
- 3. Check.
-
+ 4. Verify the installation by checking the PMM Client version:
```sh
pmm-admin --version
```
-
- 4. [Register the node](../register-client-node/index.md).
+ 5. [Register the node](../register-client-node/index.md).
## Package manager -- manual download
To manually download package manager:
{.power-number}
-1. Visit the [Percona Monitoring and Management 3 download](https://www.percona.com/downloads//) page.
-2. Under *Version:*, select the one you want (usually the latest).
-3. Under *Software:*, select the item matching your software platform and architecture (x86_64 or ARM64).
+1. Visit the [Percona Monitoring and Management 3 download](https://www.percona.com/downloads/) page.
+2. Under **Select Product Version** select the one you want (usually the latest).
+3. Under **Select Platform**, select the item matching your software platform and architecture (x86_64 or ARM64).
4. Click to download the package file:
-
- For Debian, Ubuntu: `.deb`
- For Red Hat, CentOS, Oracle Linux: `.rpm`
-
(Alternatively, copy the link and use `wget` to download it.)
=== "Debian-based"
-
```sh
dpkg -i *.deb
```
=== "Red Hat-based"
-
```sh
dnf localinstall *.rpm
```
-??? info "Download page links"
- Here are the download page links for each supported platform.
+??? info "Download page links"
+ Here are the download page links for each supported platform:
- - [Debian 9 (Stretch)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/stretch/)
- - [Debian 10 (Buster)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/buster/)
- - [Debian 11 (Bullseye)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/bullseye/)
- - [Red Hat/CentOS/Oracle 7](https://www.percona.com/downloads/pmm3/{{release}}/binary/redhat/7/)
- [Red Hat/CentOS/Oracle 8](https://www.percona.com/downloads/pmm3/{{release}}/binary/redhat/8/)
- - [Ubuntu 18.04 (Bionic Beaver)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/bionic/)
+ - [Red Hat/CentOS/Oracle 9](https://www.percona.com/downloads/pmm3/{{release}}/binary/redhat/9/)
+ - [Debian 11 (Bullseye)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/bullseye/)
+ - [Debian 12 (Bookworm)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/bookworm/)
- [Ubuntu 20.04 (Focal Fossa)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/focal/)
- - [Ubuntu 22.04 (Jammy Jellyfish)](https://www.percona.com/downloads//{{release}}/binary/debian/jammy/)
-
+ - [Ubuntu 22.04 (Jammy Jellyfish)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/jammy/)
+ - [Ubuntu 24.04 (Noble Numbat)](https://www.percona.com/downloads/pmm3/{{release}}/binary/debian/noble/)
diff --git a/documentation/docs/install-pmm/install-pmm-client/prerequisites.md b/documentation/docs/install-pmm/install-pmm-client/prerequisites.md
index ddff288d9c..2786d637ed 100644
--- a/documentation/docs/install-pmm/install-pmm-client/prerequisites.md
+++ b/documentation/docs/install-pmm/install-pmm-client/prerequisites.md
@@ -1,16 +1,12 @@
-# Prerequisites
+# Prerequisites for PMM Client
-The prerequisites to install PMM client are:
+Before installing PMM Client, ensure you meet the following requirements:
{.power-number}
-1. [Install PMM Server](../install-pmm-server/index.md) with a known IP address accessible from the client node.
-
-2. Check that you have superuser (root) access on the client host.
-
-3. Check that you have superuser access to any database servers that you want to monitor.
-
-4. Install the following Linux packages:
-
+1. [Install PMM Server](../install-pmm-server/index.md) and note the server's IP address - it must be accessible from the Client node.
+2. Check that you have superuser (`root`) access on the client host.
+3. Check that you have superuser access to all database servers you plan to monitor.
+4. Verify you have these Linux packages installed:
* `curl`
* `gnupg`
@@ -19,6 +15,5 @@ The prerequisites to install PMM client are:
* `wget`
-5. If you use it, install [Docker](https://docs.docker.com/get-docker/).
-
-6. Check [system requirements](../plan-pmm-installation/hardware_and_system.md#client-requirements).
+5. [Install Docker](https://docs.docker.com/get-started/get-docker/).
+6. Check [hardware and system requirements for PMM Client](../plan-pmm-installation/hardware_and_system.md).
\ No newline at end of file
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/backup_container.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/backup_container.md
deleted file mode 100644
index 1f225880bf..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/backup_container.md
+++ /dev/null
@@ -1,45 +0,0 @@
-
-# Backup container
-
-??? info "Summary"
-
- !!! summary alert alert-info ""
- - Stop and rename the `pmm-server` container.
- - Take a local copy of the `pmm-data` container's `/srv` directory.
-
- ---
-
-!!! caution alert alert-warning "Important"
- Grafana plugins have been moved to the data volume `/srv` since the 2.23.0 version. So if you are upgrading PMM from any version before 2.23.0 and have installed additional plugins then plugins should be installed again after the upgrade.
-
- To check used Grafana plugins:
-
- ```sh
- docker exec -it pmm-server ls /var/lib/grafana/plugins
- ```
-To backup container:
-{.power-number}
-
-1. Stop the container:
-
- ```sh
- docker stop pmm-server
- ```
-
-2. Move the image:
-
- ```sh
- docker rename pmm-server pmm-server-backup
- ```
-
-3. Create a subdirectory (e.g., `pmm-data-backup`) and move to it:
-
- ```sh
- mkdir pmm-data-backup && cd pmm-data-backup
- ```
-
-4. Back up the data:
-
- ```sh
- docker cp pmm-data:/srv .
- ```
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/env_var.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/env_var.md
deleted file mode 100644
index 145d5b02d9..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/env_var.md
+++ /dev/null
@@ -1,150 +0,0 @@
-# Environment variables in PMM
-
-Configure PMM Server by setting Docker container environment variables using the `-e var=value` syntax:
-
-```bash
-docker run -e PMM_DATA_RETENTION=720h -e PMM_DEBUG=true perconalab/pmm-server:3.0.0-beta
-```
-
-## Core configuration variables
-
-### Performance & storage
-
-| Variable | Default | Description | Example |
-|----------|---------|-------------|----------|
-| `PMM_DATA_RETENTION` | `30d` | Duration to retain metrics data. Must be in multiples of 24h. | `720h` (30 days) |
-| `PMM_METRICS_RESOLUTION` | `1s` | Base metrics collection interval | `5s` |
-| `PMM_METRICS_RESOLUTION_HR` | `5s` | High-resolution metrics interval | `10s` |
-| `PMM_METRICS_RESOLUTION_MR` | `10s` | Medium-resolution metrics interval | `30s` |
-| `PMM_METRICS_RESOLUTION_LR` | `60s` | Low-resolution metrics interval | `300s` |
-
-### Feature flags
-
-| Variable | Default | Effect when enabled |
-|----------|---------|-------------------|
-| `PMM_ENABLE_UPDATES` | `true` | Allows version checks and UI updates |
-| `PMM_ENABLE_TELEMETRY` | `true` | Enables usage data collection |
-| `PMM_ENABLE_ALERTING` | `true` | Enables Percona Alerting system |
-| `PMM_ENABLE_BACKUP_MANAGEMENT` | `true` | Enables backup features |
-| `PMM_ENABLE_AZURE_DISCOVER` | `false` | Enables Azure database discovery |
-
-### Debugging
-
-| Variable | Default | Purpose |
-|----------|---------|---------|
-| `PMM_DEBUG` | `false` | Enables verbose logging |
-| `PMM_TRACE` | `false` | Enables detailed trace logging |
-
-## Advanced configuration
-
-### Networking
-
-| Variable | Description |
-|----------|-------------|
-| `PMM_PUBLIC_ADDRESS` | External DNS/IP for PMM server |
-| `PMM_INTERFACE_TO_BIND` | Network interface binding |
-
-### Database connections
-
-| Variable | Purpose |
-|----------|----------|
-| `PMM_CLICKHOUSE_*` | ClickHouse connection settings |
-| `PMM_POSTGRES_*` | PostgreSQL connection settings |
-
-
-### Supported external variables
-
-- **Grafana**: All `GF_*` variables
-- **VictoriaMetrics**: All `VM_*` variables
-- **Kubernetes**: All `KUBERNETES_*` variables
-- **System**: Standard variables like `HOME`, `PATH`, etc.
-
-## Variables for migrating from PMM v2 to PMM v3
-
-When migrating from PMM v2 to PMM v3, you'll need to update your environment variables to match the new naming convention. This is because PMM v3 introduces several important changes to improve consistency and clarity:
-
-- environment variables now use `PMM_` prefix
-- some boolean flags reversed (e.g., `DISABLE_` → `ENABLE_`)
-- removed deprecated variables
-
-### Examples
-
-```bash
-# PMM v2
--e DISABLE_UPDATES=true -e DATA_RETENTION=720h
-
-# PMM v3 equivalent
--e PMM_ENABLE_UPDATES=false -e PMM_DATA_RETENTION=720h
-```
-
-### Migration reference table
-
-??? note "Click to expand migration reference table"
-
- #### Configuration variables
- | PMM 2 | PMM 3 | Comments |
- |---------------------------------|------------------------------------|------------------------------|
- | `DATA_RETENTION` | `PMM_DATA_RETENTION` | |
- | `DISABLE_ALERTING` | `PMM_ENABLE_ALERTING` | |
- | `DISABLE_UPDATES` | `PMM_ENABLE_UPDATES` | |
- | `DISABLE_TELEMETRY` | `PMM_ENABLE_TELEMETRY` | |
- | `DISABLE_BACKUP_MANAGEMENT` | `PMM_ENABLE_BACKUP_MANAGEMENT` | Note the reverted boolean |
- | `ENABLE_AZUREDISCOVER` | `PMM_ENABLE_AZURE_DISCOVER` | |
- | `ENABLE_RBAC` | `PMM_ENABLE_ACCESS_CONTROL` | |
- | `LESS_LOG_NOISE` | | Removed in PMM v3 |
-
- #### Metrics configuration
- | PMM 2 | PMM 3 |
- |---------------------------------|------------------------------------|
- | `METRICS_RESOLUTION` | `PMM_METRICS_RESOLUTION` |
- | `METRICS_RESOLUTION_HR` | `PMM_METRICS_RESOLUTION_HR` |
- | `METRICS_RESOLUTION_LR` | `PMM_METRICS_RESOLUTION_LR` |
- | `METRICS_RESOLUTION_MR` | `PMM_METRICS_RESOLUTION_MR` |
-
-
- #### ClickHouse configuration
- | PMM 2 | PMM 3 | Comments |
- |-------------------------------------|------------------------------------|--------------------------|
- | `PERCONA_TEST_PMM_CLICKHOUSE_ADDR` | `PMM_CLICKHOUSE_ADDR` | |
- | `PERCONA_TEST_PMM_CLICKHOUSE_DATABASE` | `PMM_CLICKHOUSE_DATABASE` | |
- | `PERCONA_TEST_PMM_CLICKHOUSE_DATASOURCE` | `PMM_CLICKHOUSE_DATASOURCE` | |
- | `PERCONA_TEST_PMM_CLICKHOUSE_HOST` | `PMM_CLICKHOUSE_HOST` | |
- | `PERCONA_TEST_PMM_CLICKHOUSE_PORT` | `PMM_CLICKHOUSE_PORT` | |
- | `PERCONA_TEST_PMM_DISABLE_BUILTIN_CLICKHOUSE` | `PMM_DISABLE_BUILTIN_CLICKHOUSE` | |
- | `PERCONA_TEST_PMM_CLICKHOUSE_BLOCK_SIZE` | | Removed in PMM v3, new version|
- | `PERCONA_TEST_PMM_CLICKHOUSE_POOL_SIZE` | | Removed in PMM v3, new version|
-
- #### PostgreSQL configuration
- | PMM 2 | PMM 3 |
- |-------------------------------------|------------------------------------|
- | `PERCONA_TEST_POSTGRES_ADDR` | `PMM_POSTGRES_ADDR` |
- | `PERCONA_TEST_POSTGRES_DBNAME` | `PMM_POSTGRES_DBNAME` |
- | `PERCONA_TEST_POSTGRES_USERNAME` | `PMM_POSTGRES_USERNAME` |
- | `PERCONA_TEST_POSTGRES_DBPASSWORD` | `PMM_POSTGRES_DBPASSWORD` |
- | `PERCONA_TEST_POSTGRES_SSL_CA_PATH` | `PMM_POSTGRES_SSL_CA_PATH` |
- | `PERCONA_TEST_POSTGRES_SSL_CERT_PATH` | `PMM_POSTGRES_SSL_CERT_PATH` |
- | `PERCONA_TEST_POSTGRES_SSL_KEY_PATH` | `PMM_POSTGRES_SSL_KEY_PATH` |
- | `PERCONA_TEST_POSTGRES_SSL_MODE` | `PMM_POSTGRES_SSL_MODE` |
- | `PERCONA_TEST_PMM_DISABLE_BUILTIN_POSTGRES` | `PMM_DISABLE_BUILTIN_POSTGRES` |
-
- #### Telemetry & development
- | PMM 2 | PMM 3 |
- |-------------------------------------|------------------------------------|
- | `PMM_TEST_TELEMETRY_DISABLE_SEND` | `PMM_DEV_TELEMETRY_DISABLE_SEND` |
- | `PERCONA_TEST_TELEMETRY_DISABLE_START_DELAY` | `PMM_DEV_TELEMETRY_DISABLE_START_DELAY` |
- | `PMM_TEST_TELEMETRY_FILE` | `PMM_DEV_TELEMETRY_FILE` |
- | `PERCONA_TEST_TELEMETRY_HOST` | `PMM_DEV_TELEMETRY_HOST` |
- | `PERCONA_TEST_TELEMETRY_INTERVAL` | `PMM_DEV_TELEMETRY_INTERVAL` |
- | `PERCONA_TEST_TELEMETRY_RETRY_BACKOFF` | `PMM_DEV_TELEMETRY_RETRY_BACKOFF` |
- | `PERCONA_TEST_VERSION_SERVICE_URL` | `PMM_DEV_VERSION_SERVICE_URL` |
- | `PERCONA_TEST_STARLARK_ALLOW_RECURSION` | `PMM_DEV_ADVISOR_STARLARK_ALLOW_RECURSION` |
-
- #### Removed variables
- | PMM 2 | PMM 3 | Comments |
- |-------------------------------------|------------------------------------|------------------------------|
- | `PERCONA_TEST_AUTH_HOST` | | Removed, use `PMM_DEV_PERCONA_PLATFORM_ADDRESS` |
- | `PERCONA_TEST_CHECKS_HOST` | | Removed, use `PMM_DEV_PERCONA_PLATFORM_ADDRESS` |
- | `PERCONA_TEST_CHECKS_INTERVAL` | | Removed, not used |
- | `PERCONA_TEST_CHECKS_PUBLIC_KEY` | | Removed, use `PMM_DEV_PERCONA_PLATFORM_PUBLIC_KEY` |
- | `PERCONA_TEST_NICER_API` | | Removed in PMM v3 |
- | `PERCONA_TEST_SAAS_HOST` | | Removed, use `PMM_DEV_PERCONA_PLATFORM_ADDRESS` |
\ No newline at end of file
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/index.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/index.md
deleted file mode 100644
index d73990beb9..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/index.md
+++ /dev/null
@@ -1,49 +0,0 @@
-# Install PMM Server with Docker container
-
-This section provides instructions for running PMM Server with Docker based on the [PMM Docker image](https://hub.docker.com/r/percona/pmm-server).
-
-## Running PMM Server with Watchtower
-
-To enable PMM Server upgrades via the **Upgrade page** and the **Upgrade Now** button on the Home dashboard, you must configure Watchtower during the PMM Server installation. Watchtower is a container monitoring tool that helps update Docker containers to their latest version when triggered.
-
-The [Easy-install script](../easy-install.md) script includes Watchtower commands, allowing for a one-step setup of PMM alongside Watchtower.
-
-You can also install PMM 3 manually, following the instructions below.
-
-## Installing PMM Server manually
-
-Before starting the installation, review the installation prerequisites below and choose a method to run PMM Server with Docker based on your preferred data storage option:
-
-- [Running Docker with Data container](../docker/run_with_data_container.md)
-- [Running Docker with host directory](../docker/run_with_host_dir.md)
-- [Running Docker with volume](../docker/run_with_vol.md)
-
-### Manual installation prerequisites
-
-- Install [Docker](https://docs.docker.com/get-docker/) version 17.03 or higher.
-- Ensure your CPU (and any virtualization layer you may be using) supports `x86-64-v2`.
-- Install Watchtower to automatically update your containers with the following considerations:
-
- - Ensure Watchtower is only accessible from within the Docker network or local host to prevent unauthorized access and enhance container security.
- - Configure network settings to expose only the PMM Server container to the external network, keeping Watchtower isolated within the Docker network.
- - Grant Watchtower access to the Docker socket to monitor and manage containers effectively, ensuring proper security measures are in place to protect the Docker socket.
- - Verify that both Watchtower and PMM Server are on the same network, or ensure PMM Server can connect to Watchtower for communication. This network setup is essential for PMM Server to initiate updates through Watchtower.
-
-## Run Docker container
-
-??? info "Summary"
-
- !!! summary alert alert-info ""
- - Pull the Docker image.
- - Copy it to create a persistent data container.
- - Run the image.
- - Open the PMM UI in a browser.
-
- ---
-??? info "Key points"
-
- - To disable the Home Dashboard **PMM Upgrade** panel you can either add `-e DISABLE_UPDATES=true` to the `docker run` command (for the life of the container) or navigate to _PMM --> PMM Settings --> Advanced Settings_ and disable "Check for Updates" (can be turned back on by any admin in the UI).
-
- - Eliminate browser certificate warnings by configuring a [trusted certificate](https://docs.percona.com/percona-monitoring-and-management/how-to/secure.html#ssl-encryption).
-
- - You can optionally enable an (insecure) HTTP connection by adding `--publish 80:80` to the `docker run` command. However, running PMM insecure is not recommended. You should also note that PMM Client *requires* TLS to communicate with the server, only working on a secure port.
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/restore_container.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/restore_container.md
deleted file mode 100644
index 1ba2b6fdd8..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/restore_container.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Restore container
-
-??? info "Summary"
-
- !!! summary alert alert-info ""
- - Stop and remove the container.
- - Restore (rename) the backup container.
- - Restore saved data to the data container.
- - Restore permissions to the data.
-
- ---
-
-!!! caution alert alert-warning "Important"
- You must have a [backup](backup_container.md) to restore from.
-
-To restore the container:
-{.power-number}
-
-1. Stop the container.
-
- ```sh
- docker stop pmm-server
- ```
-
-2. Remove it.
-
- ```sh
- docker rm pmm-server
- ```
-
-3. Revert to the saved image.
-
- ```sh
- docker rename pmm-server-backup pmm-server
- ```
-
-4. Change directory to the backup directory (e.g. `pmm-data-backup`).
-
-5. Remove Victoria Metrics data folder.
-
- ```sh
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta rm -r /srv/victoriametrics/data
- ```
-
-6. Copy the data.
-
- ```sh
- docker cp srv pmm-data:/
- ```
-
-7. Restore permissions.
-
- ```sh
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R root:root /srv && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R pmm:pmm /srv/alertmanager && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R root:pmm /srv/clickhouse && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R grafana:grafana /srv/grafana && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R pmm:pmm /srv/logs && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R postgres:postgres /srv/postgres14 && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R pmm:pmm /srv/prometheus && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R pmm:pmm /srv/victoriametrics && \
- docker run --rm --volumes-from pmm-data -it perconalab/pmm-server:3.0.0-beta chown -R postgres:postgres /srv/logs/postgresql14.log
- ```
-
-8. Start the image.
-
- ```sh
- docker start pmm-server
- ```
-
-
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_data_container.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_data_container.md
deleted file mode 100644
index 0d75300d01..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_data_container.md
+++ /dev/null
@@ -1,56 +0,0 @@
-
-# Run Docker with data container
-
-To run Docker with data container:
-{.power-number}
-
-1. Create a persistent data container:
-
- ```sh
- docker create --volume /srv \
- --name pmm-data \
- perconalab/pmm-server:3.0.0-beta /bin/true
- ```
-
- !!! caution alert alert-warning "Important"
- PMM Server expects the data volume to be `/srv`. Using any other value will result in **data loss** when upgrading.
-
- To check server and data container mount points:
-
- ```sh
- docker inspect pmm-data | grep Destination && \
- docker inspect pmm-server | grep Destination
- ```
-
-2. Create the Docker network:
-
- ```sh
- docker network create pmm_default
- ```
-
-3. Run the image:
-
- ```sh
- docker run --detach --restart always \
- --publish 443:8443 \
- --env PMM_WATCHTOWER_HOST=your_watchtower_host \
- --env PMM_WATCHTOWER_TOKEN=your_watchtower_token \
- --volumes-from pmm-data \
- --network=pmm_default \
- --name pmm-server \
- perconalab/pmm-server:3.0.0-beta
- ```
-
-4. Change the password for the default `admin` user, replacing `your_secure_password123` with a strong, unique password:
-
- ```sh
- docker exec -t pmm-server change-admin-password your_secure_password123
- ```
-
-5. Check the [WatchTower prerequisites](../docker/index.md|#prerequisites) and pass the following command to Docker Socket to start [Watchtower](https://containrrr.dev/watchtower/):
-
- ```sh
- docker run -v /var/run/docker.sock:/var/run/docker.sock -e WATCHTOWER_HTTP_API_UPDATE=1 -e WATCHTOWER_HTTP_API_TOKEN=your_watchtower_token --hostname=your_watchtower_host --network=pmm_default docker.io/perconalab/watchtower
- ```
-
-6. Visit `https://localhost:443` to see the PMM user interface in a web browser. If you are accessing the docker host remotely, replace `localhost` with the IP or server name of the host.
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_host_dir.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_host_dir.md
deleted file mode 100644
index b27a4cfb24..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_host_dir.md
+++ /dev/null
@@ -1,46 +0,0 @@
-
-# Run Docker with the host directory
-
-To run Docker with the host directory:
-{.power-number}
-
-1. Pull the image:
-
- ```sh
- docker pull perconalab/pmm-server:3.0.0-beta
- ```
-
-2. Run the image:
-
- ```sh
- docker run --detach --restart always \
- --publish 443:8443 \
- --env PMM_WATCHTOWER_HOST=your_watchtower_host \
- --env PMM_WATCHTOWER_TOKEN=your_watchtower_token \
- --volumes-from pmm-data \
- --network=pmm_default \
- --name pmm-server \
- perconalab/pmm-server:3.0.0-beta
- ```
-
-3. Change the password for the default `admin` user:
-
- ```sh
- docker exec -t pmm-server change-admin-password
- ```
-
-4. Check the [WatchTower prerequisites](../docker/index.md|#prerequisites) and pass the following command to Docker Socket to start [Watchtower](https://containrrr.dev/watchtower/):
-
- ```sh
- docker run -v /var/run/docker.sock:/var/run/docker.sock -e WATCHTOWER_HTTP_API_UPDATE=1 -e WATCHTOWER_HTTP_API_TOKEN=your_watchtower_token --hostname=your_watchtower_host --network=pmm_default docker.io/perconalab/watchtower
- ```
-
-5. Visit `https://localhost:443` to see the PMM user interface in a web browser. (If you are accessing the docker host remotely, replace `localhost` with the IP or server name of the host.)
-
-## Migrate from data container to host directory/volume
-
-To migrate your PMM from data container to host directory or volume run the following command:
-
-```sh
-docker cp :/srv /target/host/directory
-```
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_vol.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_vol.md
deleted file mode 100644
index 90c1cdc6bf..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/docker/run_with_vol.md
+++ /dev/null
@@ -1,44 +0,0 @@
-
-# Run Docker with volume
-
-To run Docker with volume:
-{.power-number}
-
-1. Pull the image:
-
- ```sh
- docker pull perconalab/pmm-server:3.0.0-beta
- ```
-
-2. Create a volume:
-
- ```sh
- docker volume create pmm-data
- ```
-
-3. Run the image:
-
- ```sh
- docker run --detach --restart always \
- --publish 443:8443 \
- --env PMM_WATCHTOWER_HOST=your_watchtower_host \
- --env PMM_WATCHTOWER_TOKEN=your_watchtower_token \
- --volumes-from pmm-data \
- --network=pmm_default \
- --name pmm-server \
- perconalab/pmm-server:3.0.0-beta
- ```
-
-4. Change the password for the default `admin` user, replacing `your_secure_password123` with a strong, unique password:
-
- ```sh
- docker exec -t pmm-server change-admin-password your_secure_password123
- ```
-
-5. Check the [WatchTower prerequisites](../docker/index.md|#prerequisites) and pass the following command to Docker Socket to start [Watchtower](https://containrrr.dev/watchtower/):
-
- ```sh
- docker run -v /var/run/docker.sock:/var/run/docker.sock -e WATCHTOWER_HTTP_API_UPDATE=1 -e WATCHTOWER_HTTP_API_TOKEN=your_watchtower_token --hostname=your_watchtower_host --network=pmm_default docker.io/perconalab/watchtower
- ```
-
-6. Visit `https://localhost:443` to see the PMM user interface in a web browser. If you are accessing the Docker host remotely, replace `localhost` with the IP or server name of the host.
\ No newline at end of file
diff --git a/documentation/docs/install-pmm/install-pmm-server/baremetal/helm/index.md b/documentation/docs/install-pmm/install-pmm-server/baremetal/helm/index.md
deleted file mode 100644
index 0c936e711a..0000000000
--- a/documentation/docs/install-pmm/install-pmm-server/baremetal/helm/index.md
+++ /dev/null
@@ -1,170 +0,0 @@
-# Install PMM Server with Helm on the Kubernetes clusters
-
-
-[Helm](https://github.com/helm/helm) is the package manager for Kubernetes. Percona Helm charts can be found in [percona/percona-helm-charts](https://github.com/percona/percona-helm-charts) repository on Github.
-
-## Before you start
-
-- Install Helm following its [official installation instructions](https://docs.helm.sh/using_helm/#installing-helm).
-- Kubernetes cluster that [Helm supports](https://helm.sh/docs/topics/kubernetes_distros/)
-
-!!! note alert alert-primary ""
- Helm v3 is needed to run the following steps.
-
-Refer to [Kubernetes Supported versions](https://kubernetes.io/releases/version-skew-policy/#supported-versions) and [Helm Version Support Policy](https://helm.sh/docs/topics/version_skew/) to find the supported versions.
-
-PMM should be platform-agnostic, but it requires escalated privileges inside a container. It is necessary to have a `root` user inside the PMM container. Thus, PMM would not work for Kubernetes Platforms such as OpenShift or others that have hardened Security Context Constraints, for example:
-
-- [Security context constraints (SCCs)
-](https://docs.openshift.com/container-platform/latest/security/container_security/security-platform.html#security-deployment-sccs_security-platform)
-- [Managing security context constraints](https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html)
-
-Kubernetes platforms offer a different set of capabilities. To use PMM in production, you would need backups and, thus storage driver that supports snapshots. Consult your provider for Kubernetes and Cloud storage capabilities.
-
-## Locality and Availability
-
-You should not run the PMM monitoring server along with the monitored database clusters and services on the same system.
-
-Please ensure proper locality either by physically separating workloads in Kubernetes clusters or running separate Kubernetes clusters for the databases and monitoring workloads.
-
-You can physically separate workloads by properly configuring Kubernetes nodes, affinity rules, label selections, etc.
-
-Also, ensure that the Kubernetes cluster has [high availability](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/ha-topology/) so that in case of a node failure, the monitoring service will be running and capturing the required data.
-
-## Install PMM Server
-
-??? info "Summary"
-
- !!! summary alert alert-info ""
- - Setup pmm-admin password
- - Install
- - Configuration parameters
- - PMM environment variables
- - PMM SSL certificates
- - Backup
- - Upgrade
- - Restore
- - Uninstall
-
- ---
-
-### Set up pmm-admin password
-
-Create Kubernetes secret with pmm-admin password:
-```sh
-cat <
-```sh
-helm uninstall pmm
-```
-
-
-!!! hint alert alert-success "Tip"
- List all releases using `helm list`.
-
-### Parameters
-
-The list of Parameters is subject to change from release to release. Check the [Parameters](https://github.com/percona/percona-helm-charts/tree/main/charts/pmm#parameters) section of the PMM Helm Chart.
-
-!!! hint alert alert-success "Tip"
- You can list the default parameters [values.yaml](https://github.com/percona/percona-helm-charts/blob/main/charts/pmm/values.yaml) or get them from chart definition: `helm show values percona/pmm`
-
-Specify each parameter using the `--set key=value[,key=value]` or `--set-string key=value[,key=value]` arguments to `helm install`. For example,
-
-```sh
-helm install pmm \
---set secret.create=false --set secret.name=pmm-secret \
---set service.type="NodePort" \
---set storage.storageClassName="linode-block-storage-retain" \
- percona/pmm
-```
-
-The above command installs PMM and sets the Service network type to `NodePort` and storage class to `linode-block-storage-retain` for persistence storage on LKE.
-
-
-
-!!! caution alert alert-warning "Important"
- Once this chart is deployed, it is impossible to change the application's access credentials, such as password, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools (if available)
-
-Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example:
-
-```sh
-helm show values percona/pmm > values.yaml
-
-#change needed parameters in values.yaml, you need `yq` tool pre-installed
-yq -i e '.secret.create |= false' values.yaml
-
-helm install pmm -f values.yaml percona/pmm
-```
-
-### [PMM environment variables](../docker/env_var.md)
-
-In case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the `pmmEnv` property.
-
-```yaml
-pmmEnv:
- DISABLE_UPDATES: "1"
-```
-
-### PMM SSL certificates
-
-PMM ships with self signed SSL certificates to provide secure connection between client and server ([check here](../../../../pmm-admin/security/ssl_encryption.md)).
-
-You will see the warning when connecting to PMM. To further increase security, you should provide your certificates and add values of credentials to the fields of the `cert` section:
-
-```yaml
-certs:
- name: pmm-certs
- files:
- certificate.crt:
+
Enter the username and password. The defaults are username: **admin** and password: **admin**
+# Need help?
+
+| **Commercial Support** | **Community Support** |
+|:--|:--|
+| **Enterprise-grade support** for mission-critical monitoring deployments with Percona Monitoring and Management.