Percona Monitoring & Management (PMM) Essentials

The following ports must be open to enable communication between the PMM Server and PMM clients.

PMM Server should keep ports 80 or 443 ports open for computers where PMM Client is installed to access the PMM web interface.

On each computer where PMM Client is installed, the following ports must be open. These are default ports that you can change when adding the respective monitoring service with the pmm-admin add command.

Also open 80 and 8080 in percona monitoring server and 3306 in mysql server 

Open Firewall Ports :

firewall-cmd --zone=public --add-service=mysql --permanent
firewall-cmd --zone=public --add-port=3306/tcp --permanent
firewall-cmd --zone=public --add-port=3306/udp --permanent
firewall-cmd --zone=public --add-port=80/tcp --permanent
firewall-cmd --zone=public --add-port=80/udp --permanent

firewall-cmd --zone=public --add-port=8080/tcp --permanent
firewall-cmd --zone=public --add-port=8080/udp --permanent

firewall-cmd --zone=public --add-port=42000/tcp --permanent
firewall-cmd --zone=public --add-port=42000/udp --permanent

firewall-cmd --zone=public --add-port=42003/tcp --permanent
firewall-cmd --zone=public --add-port=42003/udp --permanent

firewall-cmd --zone=public --add-port=42001/tcp --permanent
firewall-cmd --zone=public --add-port=42001/udp --permanent

firewall-cmd --zone=public --add-port=42002/tcp --permanent
firewall-cmd --zone=public --add-port=42002/udp --permanent

firewall-cmd --zone=public --add-port=42004/tcp --permanent
firewall-cmd --zone=public --add-port=42004/udp --permanent

List the opened ports 

sudo firewall-cmd --zone=public --list-ports --permanent

To know more about opening firewall ports click here

Set selinux to permissive ( optional )

vi /etc/sysconfig/selinux

[root@host2a ~]# cat /etc/sysconfig/selinux
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=permissive
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
SELINUXTYPE=targeted

Restart the linux server for changes to take effective.

Install Docker to run PMM Server remotely and start the docker service

$ yum -y install docker

$ systemctl start docker

$ systemctl enable docker

Pulling the PMM Server Image :

To pull the latest version from Docker Hub:

$ docker pull percona/pmm-server:latest

This step is not required if you are running PMM Server for the first time. However, it ensures that if there is an older version of the image tagged with latest available locally, it will be replaced by the actual latest version.

Creating the pmm-data Container :

To create a container for persistent PMM data, run the following command:

$ docker create \
   -v /opt/prometheus/data \
   -v /opt/consul-data \
   -v /var/lib/mysql \
   -v /var/lib/grafana \
   --name pmm-data \
   percona/pmm-server:latest /bin/true

The previous command does the following:

• The docker create command instructs the Docker daemon to create a container from an image.
• The -v options initialize data volumes for the container.
• The –name option assigns a custom name for the container that you can use to reference the container within a Docker network. In this case: pmm-data.
• percona/pmm-server:latest is the name and version tag of the image to derive the container from. 
• /bin/true is the command that the container running

Creating and Launching the PMM Server Container :

$ docker run -d \
   -p 80:80 \
   --volumes-from pmm-data \
   --name pmm-server \
   --restart always \
   percona/pmm-server:latest

This command does the following:

• The docker run command runs a new container based on the percona/pmm-server:latest image.
• The -d option starts the container in the background (detached mode).
• The -p option maps the port for accessing the PMM Server web UI. For example, if port 80 is not available, you can map the landing page to port 8080 using -p 8080:80.
• The -v option mounts volumes from the pmm-data container (see Creating the pmm-data Container).
• The –name option assigns a custom name to the container that you can use to reference the container within the Docker network. In this case: pmm-server.
• The –restart option defines the container’s restart policy. Setting it to always ensures that the Docker daemon will start the container on startup and restart it if the container exits.
• percona/pmm-server:latest is the name and version tag of the image to derive the container from.

If you need to enable Orchestrator launch the container as below :

$ docker run -d -p 80:80 \
  --volumes-from pmm-data \
  --name pmm-server \
  -e ORCHESTRATOR_ENABLED=true \
  -e ORCHESTRATOR_USER=pmmuser  \
  -e ORCHESTRATOR_PASSWORD=XXXX \
  --restart always \
  percona/pmm-server:latest

SERVER_PASSWORD (Optional)

Run this command as root or by using the sudo command.

$ docker run ... -e SERVER_PASSWORD=YOUR_PASSWORD ... percona/pmm-server:latest

By default, the user name is pmm. Use this option to use another user name.

$ docker run ... -e SERVER_USER=USER_NAME ... percona/pmm-server:latest

Settings Tab

The Settings tab displays the essential configuration settings of the database server selected from the Databases list. From this tab you can see which DSN is being used as well as the database server version.

• Click the title 
• Select “Edit” 
• Choose the Alert tab 
• Select the “Create Alert” button. In the Alert Config section, you can modify the frequency at which the alert checks for a trigger and the conditions to trigger the alert .

Updating PMM Server Using Docker

$ docker ps

CONTAINER ID        IMAGE                       COMMAND                CREATED             STATUS              PORTS                         NAMES
1807b3085b71        percona/pmm-server:latest   "/opt/entrypoint.sh"   7 minutes ago       Up 7 minutes        0.0.0.0:80->80/tcp, 443/tcp   pmm-server

The information about the currently installed version of PMM Server is available from the /srv/update/main.yml file. You may extract the version number by using the docker exec command:

$ docker exec -it pmm-server head -1 /srv/update/main.yml
# v1.6.1

Creating a backup version of the current pmm-server container

The docker stop command stops the currently running pmm-server container:

$ docker stop pmm-server

The following command simply renames the current pmm-server container to avoid name conflicts during the update procedure:

$ docker rename pmm-server pmm-server-backup

Pulling a new Docker image :

$ docker pull percona/pmm-server:1.5.0

After you have pulled a new version of PMM from the Docker repository, you can use docker run to create a pmm-server container using the new image.

$ docker run -d \
   -p 80:80 \
   --volumes-from pmm-data \
   --name pmm-server \
   --restart always \
   percona/pmm-server:latest

Check if the new container is running using docker ps.

$ docker ps

Removing the backup container

$ docker rm pmm-server-backup

Backing Up PMM Data from the Docker Container

$ mkdir pmm-data-backup; cd pmm-data-backup

Create the essential sub directories:

$ mkdir -p opt/prometheus
$ mkdir -p var/lib

$  docker stop pmm-server

Copy data from the pmm-data container:

$ docker cp pmm-data:/opt/prometheus/data opt/prometheus/
$ docker cp pmm-data:/opt/consul-data opt/
$ docker cp pmm-data:/var/lib/mysql var/lib/
$ docker cp pmm-data:/var/lib/grafana var/lib/

Now, your PMM data are backed up and you can start PMM Server again:

$ docker start pmm-server

Restoring the Backed Up Information to the PMM Data Container 

Stop the running pmm-server container.

$ docker stop pmm-server

Rename the pmm-server container to pmm-server-backup.

$ docker rename pmm-server pmm-server-backup

Rename the pmm-data to pmm-data-backup

$ docker rename pmm-data pmm-data-backup

Create a new pmm-data container

$ docker create \
   -v /opt/prometheus/data \
   -v /opt/consul-data \
   -v /var/lib/mysql \
   -v /var/lib/grafana \
   --name pmm-data \
   percona/pmm-server:latest /bin/true

Change the working directory to the directory that contains your pmm-data backup files.

$ cd ~/pmm-data-backup 

$ docker cp opt/prometheus/data pmm-data:/opt/prometheus/
$ docker cp opt/consul-data pmm-data:/opt/
$ docker cp var/lib/mysql pmm-data:/var/lib/
$ docker cp var/lib/grafana pmm-data:/var/lib/

Apply correct ownership to pmm-data files:

$ docker run --rm --volumes-from pmm-data -it percona/pmm-server:latest chown -R pmm:pmm /opt/prometheus/data /opt/consul-data
$ docker run --rm --volumes-from pmm-data -it percona/pmm-server:latest chown -R grafana:grafana /var/lib/grafana
$ docker run --rm --volumes-from pmm-data -it percona/pmm-server:latest chown -R mysql:mysql /var/lib/mysql

Run (create and launch) a new pmm-server container:

$ docker run -d \
   -p 80:80 \
   --volumes-from pmm-data \
   --name pmm-server \
   --restart always \
   percona/pmm-server:latest

To make sure that the new server is available run the pmm-admin check-network command from the computer where PMM Client is installed. Run this command as root or by using the sudo command.

$ pmm-admin check-network

Commands :

For more information please visit https://www.percona.com/doc/percona-monitoring-and-management/index.html