Setting up¶
There are three stages to installing and setting up PMM.
Summary
Set up PMM Server¶
Install and run at least one PMM Server.
Choose from:
Use | Benefits | Drawbacks |
---|---|---|
Docker | 1. Quick. 2. Simple. |
1. Docker installation required. 2. Additional network configuration required. |
Podman | 1. Quick. 2. Simple. 3. Rootless. |
1. Podman installation required. |
Helm | 1. Quick. 2. Simple. 3. Cloud. |
1. Requires running Kubernetes cluster. |
Virtual appliance | 1. Easily import into Hypervisor of your choice | 1. More system resources compared to Docker footprint. |
Amazon AWS | 1. Wizard-driven install. | 1. Non-free solution (infrastructure costs). |
Set up PMM Client¶
Install and run PMM Client on every node where there is a service you want to monitor.
The choices:
- With Docker;
- Natively, installed from:
- Linux package (installed with
apt
,apt-get
,dnf
,yum
); - Binary package (a downloaded
.tar.gz
file).
- Linux package (installed with
Binary is only way to install PMM client without root permissions
Add services¶
On each PMM Client, you configure then add to PMM Server’s inventory the node or service you want to monitor.
How you do this depends on the type of service. 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.
Get expert help¶
If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.