Deployment Overview of Percona Monitoring on Server¶

Prerequisites and Basic Requirements¶

To ensure a successful deployment, the following requirements must be met:

• Operating System: Ubuntu

• Privileges: Root or sudo access is required for package installation and Docker management.

• Network Ports:

• 80: Internal web traffic.

• 443: External HTTPS traffic.

FQDN of the final panel on the hostkey.in domain¶

The application is accessible via a specific subdomain template based on the server ID.

Application installation process¶

The application is deployed using Docker on an Ubuntu system. The installation follows these steps:

1. System Update: The APT package manager cache is updated, and all existing packages are upgraded to their latest versions.

2. Docker Installation: The Docker engine is installed on the host system if it is not already present.

3. Image Retrieval: The percona/pmm-server:3 Docker image is pulled from the registry.

4. Volume Creation: A dedicated Docker volume named pmm-data is created to ensure data persistence.

5. Container Deployment: The application is launched as a detached Docker container named pmm-server.

Docker Containers and Their Deployment¶

The deployment consists of one primary application container:

pmm-server¶

• Image Name: percona/pmm-server:3

• Ports: 443 (host) -> 80 (container)

• Volumes: pmm-data:/srv

• Environment Variables:

• PMM_CLICKHOUSE_CONFIG=low-memory

• PMM_ENABLE_UPDATES=0

• Restart Policy: always

• Resource Limits: ulimit nofile=1000000:1000000

Application Update Instructions¶

To update the Percona Monitoring on Server application, perform the following steps to pull the latest image and restart the container:

docker pull percona/pmm-server:3
docker stop pmm-server
docker rm pmm-server
# Note: Ensure you use the same volume mapping to preserve data
docker run --detach --name pmm-server --restart always -p 443:80 -v pmm-data:/srv --env PMM_CLICKHOUSE_CONFIG=low-memory --env PMM_ENABLE_UPDATES=0 --ulimit nofile=1000000:1000000 percona/pmm-server:3

Location of configuration files and data¶

Data persistence is managed through Docker volumes to ensure information is not lost when the container is removed or updated.

• Application Data: Managed via the pmm-data Docker volume, mapped to /srv inside the container.

Available ports for connection¶

The following ports are used by the application: