How to Set Up MySQL with PMM

1. Prepare your environment.

Before you start setting up PostgreSQL to be connected to PMM monitoring, you need to have a PMM Client and register it on the PMM Server. Let’s do it.  You may set up the PMM Client in different ways. It can be either running in a Docker container or installed by a package manager or from sources. In this article, we will use the easiest way — we will install it from a repository using a package manager. Make sure you have curl, gnupb, gwet, and sudo installed on your server. First of all, you need to add Percona repo to your repositories list.  For Debian-based OS a. Configure repositories:

wget https://repo.percona.com/apt/percona-release_latest.generic_all.deb

dpkg -i percona-release_latest.generic_all.deb

 b. Install the hpmm-client package:

apt update
apt install -y pmm2-client

c. Check if it was installed correctly:

pmm-admin --version

For RedHat-based OS 1. Configure repositories:

yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm

b. Install the hpmm-client package:

yum install -y pmm2-client

c. Check if it was installed correctly:

pmm-admin --version

After you have installed the PMM Client, you should register it on your server. You need an HPMM server hostname or IP address and credentials for your connection. You may find this information on your hostedpmm private cabinet.    To register the PMM client on the server, just type:

pmm-admin config --server-insecure-tls --server-url=https://admin:<password>@XXX.XXX.XXX.XXX:443 YYY.YYY.YYY.YYY generic mynode

  where XXX.XXX.XXX.XXX — IP address or hostname of PMM server, YYY.YYY.YYY.YYY — IP address or hostname of PMM client, generic — client type and mynode — mane of client.

2. Configure MySQL

Create a database account for PMM. It is a good practice not to use a superuser to connect the PMM client to the monitored database instance:

CREATE USER 'pmm'@'localhost' IDENTIFIED BY 'pass' WITH MAX_USER_CONNECTIONS 10;

GRANT SELECT, PROCESS, REPLICATION CLIENT, RELOAD, BACKUP_ADMIN ON *.* TO 'pmm'@'localhost';

There are two possible sources of metrics — Slow the query log and Performance Schema.  Here are the benefits and drawbacks of Slow query log and Performance Schema metrics sources:

Benefits

Slow query log 1. More detail. 2. Lower resource impact (with query sampling feature in Percona Server for MySQL). Performance Schema 1. Faster parsing. 2. Enabled by default on newer versions of MySQL Drawbacks Slow query log 1. PMM Client must be on the same host as the database server or have access to a slow query log. 2. Log files grow and must be actively managed. Performance Schema 1. Less detail. Data source recommendations Database server MySQL Versions 5.1-5.5 Recommended source Slow query log Database server MySQL Versions 5.6+ Recommended source Performance Schema Database server MariaDB Versions 10.0+ Recommended source Performance Schema Database server Percona Server for MySQL Versions 5.7, 8.0 Recommended source Slow query log Database server Percona XtraDB Cluster Versions 5.6, 5.7, 8.0 Recommended source Slow query log As far as we use MySQL version higher than 5.6 and our PMM server is located on a remote host, we will configure the Performance Schema course.  Add the following lines to my.conf file:

performance_schema=ON
performance-schema-instrument='statement/%=ON'
performance-schema-consumer-statements-digest=ON
innodb_monitor_enable=all
query_response_time_stats=ON
userstat=ON

Restart the mysql and create the PMM service:

pmm-admin add mysql --query-source=perfschema --username=pmm --password=pass --service-name=MYSQL_NODE —host=XXX.XXX.XXX.XXX --port=3306

You may also add the service via the PMM Server user interface in Configuration -> PMM Inventory -> Add Instance menu section. Check if the service is registered successfully:

pmm-admin inventory list services --service-type=mysql

Success!

Congratulations, you have successfully set up MySQL monitoring with PPM. Now you have access to organized, secure, and robust database management systems. Monitoring and managing your data can help your business scale, grow, and flourish.

HostedPMM Services

Now that you have set up MySQL monitoring with PMM, you can focus on bigger issues, like growing your business. HostedPMM offers hosted PMM servers for monitoring, automation, troubleshooting, and convenience for all your database needs. You can get your own PMM server, connect your instances, and focus on your project with HostedPMM. Get started for free and say hello to simpler database solutions. We offer a quick setup, backups, scalability, tech support, security updates, high availability, and no vendor restrictions.

If you have any questions or need assistance with HostedPMM, contact us at support@hostedpmm.com any time.

Related Posts:

How to set up open-source DB monitoring using PMM?

How to Set Up PostgreSQL Monitoring Using PMM

1. Prepare your environment.

Before you start setting up PostgreSQL to be connected to PMM monitoring, you need to have a PMM Client and register it on the PMM Server. Let’s do it.

You may set up the PMM Client in different ways. It can be either running in a Docker container or installed by a package manager or from sources. In this article, we will use the easiest way — we will install it from a repository using a package manager. Make sure you have curl, gnupb, wget, and sudo installed on your server. First of all, you need to add Percona repo to your repositories list.

For Debian-based OS a. Configure repositories.

wget https://repo.percona.com/apt/percona-release_latest.generic_all.deb
dpkg -i percona-release_latest.generic_all.deb

b. Install the PMM-client package.

apt update
apt install -y pmm2-client

c. Check if it was installed correctly.

pmm-admin --version

For RedHat-based OS 1. Configure repositories.

yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm

b. Install the hpmm-client package.

yum install -y pmm2-client

c. Check if it was installed correctly.

pmm-admin --version

After you have installed the PMM Client, you should register it on your server. You need the HPMM server hostname or an IP-address and credentials for your connection. You may find this information on your HostedPMM private cabinet.

To register the PMM client on the server, just type:

pmm-admin config --server-insecure-tls --server-url=https://admin:<password>@XXX.XXX.XXX.XXX:443 YYY.YYY.YYY.YYY generic mynode

where XXX.XXX.XXX.XXX — IP address or hostname of PMM server, YYY.YYY.YYY.YYY — IP address or hostname of PMM client, generic — client type and mynode — mane of client. 2. Configure PostgreSQL First of all, you should create a user to monitor:

CREATE USER pmm WITH SUPERUSER ENCRYPTED PASSWORD '******';

After that, it is necessary to enable the possibility for the PMM user to log in locally to the PostgreSQL instance. To it, add a rule to /var/lib/pgsql/data/pg_hba.conf file like that (the second line is given just to comment field arguments, it is not necessary to add it)

local   all             pmm                                md5
# TYPE  DATABASE        USER        ADDRESS                METHOD

Reload the configuration:

su - postgres
psql -c "select pg_reload_conf()"

and check if the PMM user is able to log in:

psql postgres pmm -c "\conninfo"

When the PMM user is configured, the next step is to configure the database extension for connection to the PMM server. In this guide, we will use an official extension created by PostgreSQL pg_stat_statements. There is a new extension, created by Percona — pg_stat_monitor. It gives you additional features like bracket-based aggregation. But it is still in the beta phase and is unsupported. So you can use it at your own risk. You may install pg_stat_statement by your package manager On Debian-based OS

apt install -y postgresql-contrib

On RedHat-based OS

yum install -y postgresql-contrib

Add these lines to /var/lib/pgsql/data/postgresql.conf file

shared_preload_libraries = 'pg_stat_statements'
track_activity_query_size = 2048 # Increase tracked query string size
pg_stat_statements.track = all   # Track all statements including nested
track_io_timing = on             # Capture read/write stats

Restart the database server and install the extension:

psql postgres postgres -c "CREATE EXTENSION pg_stat_statements SCHEMA public"

Now you are ready to add postgresql service to your PMM server. To add an instance, run this command in your console:

pmm-admin add postgresql \
--username=pmm \
--password=pass \
--server-url=https://admin:admin@X.X.X.X:443 \
--server-insecure-tls

You may also do it in your PMM server user interface in Configuration -> PMM Inventory -> Add instance menu section.

Setup is Complete

Congratulations, you have successfully set up PostgreSQL monitoring with PMM. Now your database has powerful monitoring and performance features that will allow you to focus on other areas of your business. You can rest assured knowing that your database is being monitored and will give you live alerts if any big changes arise.

HostedPMM Services

Now that you have PostgreSQL and PMM set up, you can focus on bigger issues, like growing your business. If you need a server, HostedPMM offers hosted PMM servers for monitoring, automation, troubleshooting, and convenience for all your database needs. We provide servers for PMM to help your business. You can get your own PMM server, connect your instances, and focus on your project with HostedPMM. Our databases sync with a wide range of software to deliver a completely customized experience to suit your business needs.

Get started for free and enjoy more organized, secure, scalable, optimized, and adaptable database solutions. Our databases include in-depth troubleshooting and performance optimization. We offer quick setup, tech support, backups, scalability, security updates, high availability, and no vendor restrictions.

If you have any questions or need assistance with HostedPMM, contact us at support@hostedpmm.com at any time.

Related Posts:

How to set up open-source DB monitoring using PMM?

How to Set Up MongoDB Monitoring with PMM

1. Prepare your environment. Before you get started setting up MongoDB to connect to PMM monitoring, you need to have a PMM Client and register it on the PMM Server. Let’s do it.  You may set up the PMM Client in different ways. It can be either running in a Docker container or installed by a package manager or from sources. In this article, we will use the easiest way — we will install it from the repository using a package manager. Make sure you have curl, gnupb, wget, and sudo installed on your server. First of all, you need to add the Percona repo to your repositories list.  For Debian-based OS a. Configure repositories:

wget https://repo.percona.com/apt/percona-release_latest.generic_all.deb
dpkg -i percona-release_latest.generic_all.deb

 b. Install hpmm-client package:

apt update
apt install -y pmm2-client

c. Check if it was installed correctly:

pmm-admin --version

For RedHat-based OS 1. Configure repositories:

yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm

b. Install hpmm-client package:

yum install -y pmm2-client

c. Check if it was installed correctly:

pmm-admin --version

After you have installed the PMM Client, you should register it on your server. You need the HPMM server hostname or IP-address and credentials for your connection. You may find this information on your hostedpmm private cabinet.    To register the PMM client on the server, just type:

pmm-admin config --server-insecure-tls --server-url=https://admin:<password>@XXX.XXX.XXX.XXX:443 YYY.YYY.YYY.YYY generic mynode

  where XXX.XXX.XXX.XXX — IP address or hostname of PMM server, YYY.YYY.YYY.YYY — IP address or hostname of PMM client, generic — client type and mynode — mane of client. 2.  Configure MongoDB After MongoDB and the PMM client are installed, you need to have a user with proper privileges. You may add a user in the Mongo session:

db.getSiblingDB("admin").createRole({
    role: "explainRole",
    privileges: [{
        resource: {
            db: "",
            collection: ""
            },
        actions: [
            "listIndexes",
            "listCollections",
            "dbStats",
            "dbHash",
            "collStats",
            "find"
            ]
        }],
    roles:[]
})

db.getSiblingDB("admin").createUser({
   user: "pmm_mongodb",
   pwd: "password",
   roles: [
      { role: "explainRole", db: "admin" },
      { role: "clusterMonitor", db: "admin" },
      { role: "read", db: "local" }
   ]
})

If you want to use PMM Query Analytics, you should turn on the profiling feature. To make this setting permanent, edit /etc/mongod.conf adding operationProfiling section:

operationProfiling:
  mode: all
  slowOpThresholdMs: 200
 rateLimit: 100 # (Only available with Percona Server for MongoDB.)

Restart mongod service

systemctl restart mongod

After that, you are ready to connect your MongoDB to PMM monitoring. To do that run: 

pmm-admin add mongodb \
--username=pmm_mongodb --password=password \
--query-source=profiler --cluster=mycluster

You may add –environment and -custom-label options to set tags for the service to help identify them.

After successful adding, you may find your service on the PMM Server in Configuration -> PMM Inventory -> Inventory list or check on the client using the command:

pmm-admin inventory list services --service-type=mongodb

And now you should see your MongoDB on your monitoring panel.

HostedPMM Services

Now that you have MongoDB monitoring with PMM set up, you are free to focus on other important issues with your business. HostedPMM offers hosted PMM servers for monitoring, automation, troubleshooting, and convenience for all your database needs. We provide servers for PMM to help your business. You can get your own PMM server, connect your instances, and focus on your project with HostedPMM.

Get started with HostedPMM for free and enjoy more organized, adaptable, optimized, and secure database solutions. We offer quick setup, tech support, backups, scalability, security updates, high availability, and no vendor restrictions.

If you have any questions or need assistance with HostedPMM, contact us at support@hostedpmm.com for support.

Related Posts:

How to set up open-source DB monitoring using PMM?

PMM — SolarWinds (Vivid Cortex) Open Source alternative

What is Database Monitoring Tools and Why do You Need Them

Databases are often the core of most systems, and it is very important to know every moment if it is healthy and work properly.

When your project is not so big it is enough standard common monitoring tools. But when your bases grow you probably want to get more information about them. Database health is not the only thing you are interested now.

Such things like performance, queries, connections and other kinds of statistics may have more sense for you and can save your money (or rase your costs if you use your resources ineffectively).

So in that case you need some specific tools which are specially designed for monitoring databases.

Tools for Databases Monitoring 

One of the most popular tools for databases monitoring is VividCortex from SolarWinds. It is supplied as  SaaS (software as a service).

VividCortex allows you to monitor errors, latency, slow queries, replication health, max connections, disk health. It provides dashboards out of the box, and guides you on which metrics you should monitor.

Another feature is events. For example, if you are getting closer to the maximum of any threshold, id will emit an event. This approach removes ambiguity around which metrics are important to monitor.

The most advantage of VividCortex is SaaS platform. That means that you don’t need to have any infrastructure to host your monitoring services. You just install agents to your database hosts and that’s all. 

Another cool thing is 24/4 support and good training programs. That means it is needed minimum efforts from you to setup and manage your monitoring system. SolarWinds gives you 14 days of trial period to try the service. And the price is available on demand and not available in public domain. So, we can conclude VividCortex is a good enterprise product for big and loaded projects. 

But if you are not a big company and you don’t need such level of vendor support. Is there any open source alternatives for such powerful tool as VividCortex? Fortunately yes. There is

Percona Monitoring and Management.

It is an open source database monitoring, management and observability solution for databases. It is very powerful tool for database monitoring. PMM leverages Prometheus and provides dashboards about of the box.

Monitoring capabilities allow you to watch under slow queries, errors, replication lag, max connections, disk space etc.

Built in advisors run regular checks of potential security threats.

Performance degradation, data loss and data corruption.

PMM gives you several models of using. You may deploy it on your own infrastructure and manage it by your own team absolutely free. But if you need a professional support you may get it 24×7. And PMM is also available as SaaS.

To conclude, we can say that Percona Monitoring and Management is a good alternative for enterprise solutions like VividCortex. It gives you the almost the same powerful abilities to monitor and manage your databases.

It is free OpenSource product, so it will be suitable for not big companies and projects. But it PMM can be also distributed as SaaS with 24×7 support for enterprise world.

We would like to share our experience of using PMM for DB cluster monitoring. This is a great tool with useful dashboards that help us improve the availability and performance of our infrastructure.

We perform weekly reviews of our main cluster using these dashboards:

1. PMM Query analytics:

The main concept on this screen is ‘Load’ which is the average query execution time multiplied by queries per sec, essentially this metric indicates how much MySQL resources are consumed. E.g. query that was running for 5 minutes but just a single run won’t make it to the top.

Usually, we look at the top 10 queries.

You can click on each query digest and see more details about it.

It helped us several times to detect inefficient queries and things when a query was executed a lot more often than it was anticipated.

1. Nodes overview:

Supplementary graph that just displays basic OS metrics – usually we look here to examine moments of the peak load in order to determine the performance bottleneck.

1. MySQL instances overview:

Same as (2) but holds MySQL-specific metrics.

1. PMM Advisor checks:

This may be rather handy to be aware of vulnerabilities in your version, configuration flaws etc. Warnings in the screenshot above are about minor Percona Server version (”Current version is 8.0.22, the latest available version is 8.0.29.”).

1. Our last check is PMM Query errors, but the representation there was inconvenient for us so we’ve replaced it with our own implementation which collects MySQL query errors each 2 seconds and injects them into Clickhouse for further inspection. The results look this way:

In the screenshot above we can see a lot of lock insert collisions (which is expected) and 15 DELETE deadlocks that are yet to be investigated.

This article assumes you have already installed PMM on your machine.

Securing your web services by moving them to use HTTPS instead of plain HTTP is one of the best ways to make sure the exchange remains encrypted for all the parties involved in transporting data between the service and the client browser. Extra protection against man-in-the-middle (MITM) attacks is a welcome feature as well.

Your PMM instance is already secured with a self-signed certificate: you’d want to keep your credentials safe from eavesdropping. This is no help against MITM attacks, though, and not the best practice in general. To fully utilize HTTPS you will need to acquire a certificate issued by one of the global authority centers.

The process involves:

1. Creating a DNS record for your PMM instance to be accessed over the web
2. Obtaining an SSL/TLS certificate for the PMM instance
3. Installing the certificate and verifying the setup
4. (optionally) Hosting PMM behind a reverse proxy

We will use mypmm.example.com as an address we want our PMM to be available at, example.com being a domain under our control.

Creating a DNS record for the PMM instance with the address you prefer

You would need a new “type A” record pointing to the IP address that publicly serves your PMM:

A  1.1.1.1  mypmm.example.com.

Make sure the record works as expected by opening https://mypmm.example.com in a browser.

Obtaining an SSL/TLS certificate for your PMM instance

In case you have a wildcard certificate for “*.example.com”, you can skip this step and move on to the next one.

Otherwise, we recommend using Let’s Encrypt — a service that issues SSL/TLS certificates for free. https://letsencrypt.org/

The simplest way to use it is via a recommended tool named Certbot. https://certbot.eff.org/

Certbot is provided as a drop-in Snap package (“snapd” daemon), supported by most Linux distributions, but there are alternatives available on the website.

Here’s how you proceed with Snap. Update it first:

sudo snap install core; sudo snap refresh core

Install Certbot package:

sudo snap install --classic certbot

Link new binary to a place inside your $PATH variable:

sudo ln -s /snap/bin/certbot /usr/bin/certbot

You should have certbot command available to run in your terminal now. If you get “command not found” instead, restart your shell session by logging out.

Launch Certbot as a standalone Web server, temporarily binding it to TCP port 80. This will start the certificate acquistion:

sudo certbot certonly --standalone -d mypmm.example.com

You will be asked a number of questions on behalf of Let’s Encrypt. When the utility finishes its work, you will see a short summary.

Certificate is saved at: /etc/letsencrypt/live/mypmm.example.com/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/mypmm.example.com/privkey.pem
This certificate expires on 2023-01-28.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

“`

We got our certificate, time to install it.

Installing the certificate and verifying the setup

Replace the default self-signed certificates inside Docker image with your own:

docker cp -L /etc/letsencrypt/live/mypmm.example.com/cert.pem pmm-server:/srv/nginx/certificate.crt

docker cp -L /etc/letsencrypt/live/mypmm.example.com/chain.pem pmm-server:/srv/nginx/ca-certs.pem

docker cp -L /etc/letsencrypt/live/mypmm.example.com/privkey.pem pmm-server:/srv/nginx/certificate.key

Restart Docker container:

docker restart pmm-server

Check your new certificate by opening https://mypmm.example.com. If you were logged into PMM before, you might need to clear your browser cache or use incognito mode to immediately see the difference.

Hosting PMM behind a reverse proxy

There’s a number of things you have to keep in mind when setting up PMM behind a reverse proxy (such as NGINX). You will have to pass a number of HTTP headers and enable WebSocket support for the web interface to work properly.

NGINX configuration example that serves locally available PMM mypmm.local.net as a publicly accessible mypmm.example.com:

http {

	# [...skipped...]

	# WebSocket handling for proxied connections
	map $http_upgrade $connection_upgrade {
	default upgrade;
	'' close;
	}

	# [...skipped...]

	server {
		server_name mypmm.example.com;
		ssl_certificate /etc/letsencrypt/live/mypmm.example.com/fullchain.pem;
		ssl_certificate_key /etc/letsencrypt/live/mypmm.example.com/privkey.pem;

		listen 443 ssl;

		location / {
			proxy_set_header Origin           https://mypmm.local.net;
			proxy_set_header Host             mypmm.local.net;
			proxy_set_header Upgrade          $http_upgrade;
			proxy_set_header Connection       $connection_upgrade;
			proxy_set_header X-Real-IP        $remote_addr;
			proxy_set_header X-Forwarded-For  $proxy_add_x_forwarded_for;
			proxy_pass                        http://mypmm.local.net/;
		}
	}
}

In addition, your PMM instance might require gRPC communication with remote pmm-agents. Depending on your web server, this might not be possible.

There are many different ways to install a PMM server. In this article, we will describe a solution based on a Linode VPS on which we will install the Docker Engine and run the PMM server in a Docker container. Linode, which is a blend of the words Linux and node, is a cloud hosting provider of Linux-based virtual private servers. Linode makes virtual computing more simple, affordable, and accessible.

How to Install PMM

These are the requirements you’ll need to begin:

• Registered account on the Linode Cloud platform
• Any SSH client
• Any web browser with enabled JavaScript support

Creating Linode Instance

Login to Linode Cloud console.

https://cloud.linode.com/linodes

Click the “Create Linode” button on the top-right side of the page.

Choose distribution and region.

Choose type or VPS.

Set a custom name for the Linode instance, for example, PMM-demo.

Type the root password, and add SSH Keys of allowed users.

Other settings are optional, so if you don’t need them, then you may ignore them.

Click the “Create Linode” button.

Wait some time until the VM will be created and Provisioning status changes to Running.

After starting the virtual machine, we can connect to it via SSH.

Installing Docker Engine

First of all, let’s update the packages list:

apt update

Then install the necessary packages:

apt install ca-certificates curl gnupg lsb-release

Wait some time until the installation process is complete.

Now let’s add the GPG key that signed the packages from the repository:

curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

Then you need to add the repository configuration:

echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/debian $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

Update the packages list again:

apt update

Install Docker Engine:

apt install docker-ce docker-ce-cli containerd.io docker-compose-plugin

Installing PMM Server

Pull image from Docker Hub

Most likely you have not yet downloaded the PMM-server image, so download it using the following command:

docker pull percona/pmm-server:2

Create persistent volume

The PMM server stores the collected data in databases integrated into the image (not the best practice, but it seemed more convenient to the authors of the image). I’m sure you don’t want to lose this collected data when updating the server, so you need to create a persistent volume, let’s call it PMM-data.

docker volume create pmm-data

Run PMM server in container with persistent volume

Now you can safely launch the container with the PMM server and proceed with its direct configuration.

docker run --detach --restart always \
  --publish 443:443 \
  -v pmm-data:/srv \
  --name pmm-server \
  percona/pmm-server:2

Check the status of running the PMM server

Let’s check the status of the PMM server – it should be fine, but just in case.

docker ps

Reset admin password

Now let’s change the password of the admin user to “new_pass”.

docker exec -t pmm-server bash -c 'grafana-cli --homepath /usr/share/grafana --configOverrides cfg:default.paths.data=/srv/grafana admin reset-admin-password new_pass'

Change admin email (optional)

For right now, it’s not possible to change the email of the admin user via PMM CLI, but you can do it via a simple API call. First, you need to generate a Bearer Token, which can be created from login/password pair with the help of base64 decoder:

echo -n "admin:new_pass" | base64

Execute a simple cURL request:

curl --location --request PUT "https://127.0.0.1/graph/api/users/1" \
  --insecure \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "Authorization: Basic YWRtaW46bmV3X3Bhc3M=" \
  --data "{\"email\":\"ownemail@example.com\",\"login\":\"admin\"}"

Login to the admin panel

Now you can open the PMM server page through a browser.

https://<linode-instance-ip>/graph/login

You will most likely see an error about the self-signed certificate that was auto-generated on the first run of the PMM server. Just ignore this message. For the login/password pair, use the admin and password chosen on the “Reset admin password” step.

Installation Complete

Congratulations, you have successfully installed PMM using Linode. PMM – Percona Monitoring and Management – provides database monitoring and management services and helps streamline your business with convenient cloud computing solutions. PMM simplifies cloud computing and helps optimize databases by allowing you to easily find, fix, and prevent issues with scaling, bottlenecks, and potential outages.

If you want to know how to install PMM, there are many options. Linode offers a great option to install PMM. This PMM installation is based on a Linode VPS on which we install the Docker Engine and run the PMM server in a Docker container. To install PMM using Linode you just need a registered account on the Linode Cloud platform, any SSH client, and any web browser with enabled JavaScript support.

HostedPMM Services

Now that you have installed PMM, you can focus on bigger issues, like growing your business. HostedPMM offers hosted PMM servers for monitoring, automation, troubleshooting, and convenience for all your database needs. We provide servers for PMM as a service to you. You can get your own PMM server, connect your instances, and focus on your project with HostedPMM. Get started for free and say hello to simpler database solutions. We offer a quick setup, backups, scalability, tech support, security updates, high availability, and no vendor restrictions.

If you have any questions or need assistance with HostedPMM, contact us at support@hostedpmm.com for support.

Related Posts: How to set up open-source DB monitoring using PMM?

Here is a small HowTo about installing the Percona Monitoring and Management (PMM) server using the AWS Marketplace.

Requirements:

• AWS account
• Web-browser with enabled JavaScript
• Cup of coffee

For the first you need to open the AWS Marketplace page and search for “Percona Monitoring and Management Server” or just click to this direct link.

Here you click to Continue to Subscribe and you’ll be redirected to the Subscribe to this software page. On this page you may look at details about your subscription, additional taxes and etcetera.

Let’s click Continue to Configuration.

On the next page, called Configure this software you need to choose the version of PMM and region, then click Continue to Launch button.

On the Launch this software page you need to choose:

• Choose action: Launch from website
• EC2 Instance Type: Any type of instance that suits your needs, t2.medium will be used in this example

Scroll down to the VPC Settings block, here you can set:

• Virtual Private Cloud (VPC) – If not exists, then need to create a new one
• Subnet – For communication between instances in VPC
• Security group – In settings of selected security group an Inbound and Outbound rules should have permissions for connection through SSH, HTTP and HTTPS protocols form any IP-addresses
• Key pair – Need to create a new one if not exists

Click the Launch button when you are ready.

If everything is okay you’ll see a page like above, to check the initialization status go to the page EC2 Console.

From the Instances page you may copy an IP-address of the instance and connect to it via web-browser, ignore Self-Signed Certificate warning.

Here for login you need to input the ID of the instance from AWS Console, copy and paste it.

After that, the web-browser redirects you to the final setup page.

Here you need input username and password.

• Default username: admin
• Default password: admin

On the next step you may have to reset the default password or skip this step.

And we are finally in, congrats!