Percona Monitoring and

Management
Documentation
2.37.1 (Jun 05, 2023)

Percona Technical Documentation Team

Percona LLC, © 2023

 Table of contents

Table of contents

1. Welcome 3

1.1 Start here 4

1.2 Read more 5

2. Setting up 7

2.1 Set up PMM Server 7

2.2 Set up PMM Client 7

2.3 Add services 7

3. Get Started 10

4. How to 12

5. Details 14

6. DBaaS 16

6.1 Introduction to Database as a service (DBaaS) 16

6.2 DBaaS architecture 17

6.3 Managing Database clusters 21

6.4 DBaaS backup and restore 24

7. FAQ 27

7.1 How can I contact the developers? 27

7.2 What are the minimum system requirements? 27

7.3 How can I upgrade from version 1? 27

7.4 How to control data retention? 27

7.5 How are PMM Server logs rotated? 27

7.6 What privileges are required to monitor a MySQL instance? 28

7.7 Can I monitor multiple service instances? 28

7.8 Can I rename instances? 28

7.9 Can I add an AWS RDS MySQL or Aurora MySQL instance from a non-default AWS partition? 28

7.10 What resolution is used for metrics? 29

7.11 How do I set up Alerting? 29

7.12 How do I use a custom Prometheus configuration file? 30

7.13 How to troubleshoot an Update? 30

7.14 What are my login credentials when I try to connect to a Prometheus Exporter? 30

7.15 How to provision PMM Server with non-default admin password? 30

7.16 How to change the PMM password for a default admin user? 31

7.17 How to use a non-default listen-port for pmm-admin? 31

7.18 How PMM handles personal and confidential data 31

8. Release Notes 33

- 2/35 - Percona LLC, © 2023

 1. Welcome

1. Welcome
Percona Monitoring and Management (PMM) is an open source database monitoring, management, and observability solution
for MySQL, PostgreSQL, and MongoDB.

It allows you to observe the health of your database systems, explore new patterns in their behavior, troubleshoot them and
perform database management operations no matter where they are located on-prem or in the cloud.

• PMM collects thousands of out-of-the-box performance metrics from databases and their hosts.

• The PMM web UI visualizes data in dashboards.

• Additional features include advisors for database health assessments.

This is the documentation for the latest release, PMM 2.37.1 (Release Notes).

Here’s how the home page looks on our free, live demo system.

- 3/35 - Percona LLC, © 2023

 1.1 Start here

PMM runs in the cloud, on-prem, or across hybrid platforms. It’s supported by our legendary expertise in open source
databases, and by a vibrant developer and user community.

A minimal PMM set-up comprises one server and a client agent on every system you want to monitor.

1.1 Start here

• An easy install script, which you download, make executable and run. The script installs Docker and runs PMM Server as
a container.
• The Quickstart install guide shows how to run PMM Server as a Docker container, and how to install PMM Client on
Ubuntu or Red Hat Linux hosts.

• Setting Up explains in detail how to set up PMM Server, clients, and how to add services.

- 4/35 - Percona LLC, © 2023

 1.2 Read more

1.2 Read more

1.2.1 Links to popular sections

For System Administrators

• Setting up

• How to configure

• How to upgrade
• pmm-admin

• Architecture

For Users

• User interface

• Using Query Analytics

• Using Percona Alerting

• Dashboards reference

Full section map (click to show/hide)

Welcome

Setting up Get started How to Details

User Interface Configure Architecture

User Interface
Server Client Percona Alerting Manage Users
components

Backup and Restore Upgrade Dashboards

Network MySQL
Query Analytics Secure Commands
Docker MongoDB
Advisors Optimize pmm-admin
Virtual appliance PostgreSQL
DBaaS Annotate pmm-agent
AWS Marketplace ProxySQL
Render dashboard
API
images
Easy-install script Amazon RDS
Extend metrics VictoriaMetrics
DBaaS Microsoft Azure
Troubleshoot Glossary
Google Cloud Platform

Linux

External Services

HA Proxy

Remote Instances

- 5/35 - Percona LLC, © 2023

 1.2.2 Contact us

1.2.2 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2022-12-19

- 6/35 - Percona LLC, © 2023

 2. Setting up

2. Setting up
There are three stages to installing and setting up PMM.

Summary

1. Set up a PMM Server.

2. Set up PMM Client(s).

3. Add services.

2.1 Set up PMM Server

Install and run at least one PMM Server.

Choose from:

Use Benefits  Drawbacks

Docker 1. Quick. 1. Docker installation required.

2. Simple. 2. Additional network configuration required.

Podman 1. Quick. 1. Podman installation required.

2. Simple.
3. Rootless.

Helm 1. Quick. 1. Requires running Kubernetes cluster.

2. Simple.
3. Cloud.

Virtual 1. Easily import into Hypervisor of your 1. More system resources compared to Docker
appliance choice footprint.

Amazon AWS 1. Wizard-driven install. 1. Non-free solution (infrastructure costs).

2.2 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).

Binary is only way to install PMM client without root permissions

2.3 Add services

On each PMM Client, you configure then add to PMM Server’s inventory the node or service you want to monitor.

- 7/35 - Percona LLC, © 2023

 2.3 Add services

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.

- 8/35 - Percona LLC, © 2023

 2.3.1 Contact us

2.3.1 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-03-15

- 9/35 - Percona LLC, © 2023

 3. Get Started

3. Get Started
• User Interface
• Using the web-based user interface.

• Finding dashboards.

• Rendering dashboard images.

• Viewing graph details.

• Annotating events.

• Percona Alerting
• Backup and Restore
• Query Analytics, a specialized dashboard for detailed query analysis.

• Advisors: Enabling and seeing the results of database Advisor checks.

• DBaaS: Configuration for DBaaS and UI for creating Database clusters.

These features are currently only available for PMM Admin users:

• Backup
• DBaaS

• Percona Alerting
• Advisors

To use these features you must be logged in as a PMM Admin user and activate the features.

If you are logged in as a user that has a Viewer or Editor role you’ll see an ‘insufficient access’ message when trying to use these
features.

- 10/35 - Percona LLC, © 2023

 3.0.1 Contact us

3.0.1 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-02-23

- 11/35 - Percona LLC, © 2023

 4. How to

4. How to
• Configure via the PMM Settings page.
• Manage users via the PMM Users page.

• Upgrade PMM Server via the user interface.

• Secure your PMM installation.

• Optimize the performance of your PMM installation.

• Annotate charts to mark significant events.

• Share dashboards and panels to save or share.

• Extend Metrics with textfile collector.
• Troubleshoot

- 12/35 - Percona LLC, © 2023

 4.0.1 Contact us

4.0.1 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2022-07-27

- 13/35 - Percona LLC, © 2023

 5. Details

5. Details
• Architecture: High-level architecture and main components.
• User interface components: Descriptions of the main menus and icons.

• PMM components and versions: PMM components and their version used in PMM.

• Data handling in PMM: Personal and confidential data handling in PMM.

• Developing Advisor checks: Database health assessments.

• Dashboards reference: A complete list of dashboards by category, with screenshots.

• Commands:
• pmm-admin: The manual page for the PMM administration tool.
• pmm-agent: The manual page for the PMM Client agent program.

• API: How to access the Swagger API.

• VictoriaMetrics: The monitoring solution and time-series database that replaced Prometheus in PMM 2.12.0.

• ClickHouse: A third-party column-oriented database management system (DBMS) that facilitates the Query Analytics
functionality.
• PostgreSQL: An open source object-relational database management system used as the primary data store.

• Glossary: A list of obscure terms and definitions.

- 14/35 - Percona LLC, © 2023

 5.0.1 Contact us

5.0.1 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-05-22

- 15/35 - Percona LLC, © 2023

 6. DBaaS

6. DBaaS

6.1 Introduction to Database as a service (DBaaS)

Database as a service (DBaaS) feature of Percona Monitoring and Management (PMM) is an open source solution to run
MySQL and MongoDB clusters on Kubernetes.

It allows you to utilize the benefits of Kubernetes and Percona’s operators to run and manage database clusters.

Do not use for mission critical workloads

DBaaS feature is available for PMM Admin users DBaaS functionality is currently in technical preview and is subject to change.

6.1.1 Start here

• Architecture and how DBaaS works

• Setting up
• Getting started with DBaaS

• Registering and managing Kubernetes clusters

• Creating and managing database clusters

• Creating or updating a database cluster from a DBaaS template

Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-03-23

- 16/35 - Percona LLC, © 2023

 6.2 DBaaS architecture

6.2 DBaaS architecture

DBaaS is built on top of PMM and Kubernetes and the high-level architecture is shown below

In DBaaS, the role of PMM is as follows:

1. Expose Public REST API

2. Provision Kubernetes cluster and install the following operators:

a. OLM (Operator Lifecycle Manager)

b. Percona Operator for MongoDB

c. Percona Operator for MySQL

d. DBaaS operator

6.2.1 Operator Lifecycle Manager (OLM)

DBaaS uses OLM to install and update operators. PMM installs OLM and Operator Catalog during the registration of the
Kubernetes cluster.

An Operator catalog is a repository of metadata that Operator Lifecycle Manager (OLM) can query to discover and install
Operators and their dependencies on a cluster. OLM always installs Operators from the latest version of a catalog and if a

- 17/35 - Percona LLC, © 2023

 6.2.1 Operator Lifecycle Manager (OLM)

new version of an operator becomes available, OLM can upgrade it once the user has accepted the upgrade. DBaaS uses its
own catalog for OLM that has the following operators:

1. DBaaS operator

2. PXC operator
3. PSMDB operator

4. Victoria Metrics operator

Percona Catalog is an OLM catalog that stores ClusterServiceVersions and CustomResourceDefinitions for creation in a
cluster, and stores metadata about packages and channels. It’s a source of truth for the available versions of operators ready
to use in DBaaS

The installation of operators looks the following way

- 18/35 - Percona LLC, © 2023

 6.2.2 DBaaS operator

6.2.2 DBaaS operator

DBaaS operator is responsible for creating and managing databases following operator pattern and depends on underlying
operators for running database clusters. It provides a simplified API to manage database clusters via kubectl .

Contact us

For free technical help, visit the Percona Community Forum.

- 19/35 - Percona LLC, © 2023

 6.2.2 DBaaS operator

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-02-23

- 20/35 - Percona LLC, © 2023

 6.3 Managing Database clusters

6.3 Managing Database clusters

6.3.1 Database cluster Templates

Database clusters can be created from templates using PMM. Database cluster Template allows operators to customize
Database Clusters based on their requirements, environments, or infrastructure.

Examples

• Data clusters: Different load patterns, such as simple reads, heavy writes, 50%/50% read/write, and the number of
connections.

• Infrastructure - Different parameters and tuning for the resulting cluster: such as network configuration (load
balancing, exposure), storage classes/types, etc.

• Environment: Combination of database cluster and infrastructure that will affect the database cluster configuration.

6.3.2 Customize PXC DB configuration

The following example shows how DBaaS users can create PXC DB clusters from a template that sets a custom MySQL
configuration. The default MySQL configuration is the following:

[mysqld]
wsrep_provider_options="gcache.size=600M"

Note

PXC DB configuration can be customized based on your needs. This can be accomplished by creating a template and changing that
field.

- 21/35 - Percona LLC, © 2023

 6.3.2 Customize PXC DB configuration

Create Custom Resource Definition (CRD) template

To create a template, do the following:

1. Identify the field(s) of interest by reading the PXC operator documentation and the PXC CRD. In this case, you have to
change the spec.pxc.configuration field.

2. Create a template CRD pxctpl-crd-pxc-configuration.yaml with just those small subset of fields.

apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
annotations:
controller-gen.kubebuilder.io/version: v0.8.0
creationTimestamp: null
name: pxctemplatepxcconfiguration.dbaas.percona.com
labels:
dbaas.percona.com/template: "yes"
dbaas.percona.com/engine: "pxc"
spec:
group: dbaas.percona.com
names:
kind: PXCTemplatePXCConfiguration
listKind: PXCTemplatePXCConfigurationList
plural: pxctemplatepxcconfiguration
singular: pxctemplatepxcconfiguration
scope: Namespaced
versions:
- name: v1
schema:
openAPIV3Schema:
properties:
apiVersion:
type: string
kind:
type: string
metadata:
type: object
spec:
properties:
pxc:
properties:
configuration:
type: string
type: object
type: object
status:
type: object
type: object
served: true
storage: true

3. Run the following command.

kubectl apply -f pxctpl-crd-upgrade-options.yaml

For more information, see DatabaseCluster templates.

ADD READ PERMISSIONS FOR DBAAS-OPERATOR

In order for the dbaas-operator to apply the template it needs access to the template CRs:

DBAAS_OPERATOR_MANAGER_ROLE=$(kubectl get clusterroles | grep dbaas-operator | grep -v metrics | grep -v proxy | cut -f 1 -d ' '); kubectl get
clusterroles/"$DBAAS_OPERATOR_MANAGER_ROLE" -o yaml > dbaas-operator-manager-role.yaml
cat <<EOF >>dbaas-operator-manager-role.yaml
- apiGroups:
- dbaas.percona.com
resources:
- pxctemplatepxcconfiguration
verbs:
- get
- list
EOF

Run the following command:

kubectl apply -f dbaas-operator-manager-role.yaml

CREATE PXCTEMPLATEPXCCONFIGURATION TEMPLATE CR

1. Create a corresponding CR pxctpl-pxc-config-max-connection-789.yaml with the required values.

- 22/35 - Percona LLC, © 2023

 6.3.2 Customize PXC DB configuration

apiVersion: dbaas.percona.com/v1
kind: PXCTemplatePXCConfiguration
metadata:
name: pxc-config-max-connections-789
labels:
dbaas.percona.com/template: "yes"
dbaas.percona.com/engine: "pxc"
spec:
pxc:
configuration: |
[mysqld]
max_connections = 789

2. Run the following command:

kubectl apply -f pxctpl-pxc-config-max-connection-789.yaml

Create a DB cluster from template

To create a DB cluster from a template, do the following:

1. From the main menu navigate to DBaaS → Create DB Cluster.

2. On the Advanced Settings panel, select the template from the Templates drop-down.

3. Click Create .

CONTACT US

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-04-05

- 23/35 - Percona LLC, © 2023

 6.4 DBaaS backup and restore

6.4 DBaaS backup and restore

Caution

DBaaS functionality is currently in technical preview and is subject to change.

You can add a backup schedule while creating DB clusters in DBaaS. This feature is a fusion of backup management and
DBaaS in PMM. Currently, DBaaS only supports scheduled backups, which can only be enabled when a database cluster is
created.

To create a scheduled backup do the following:

Prerequisites

1. Enable Backup management:

From the main menu, navigate to Configuration →  Settings → Advanced Settings → Backup Management to enable
Backup management.
2. Add a backup storage location:

Note

Currently, only S3 is supported.

From the main menu, navigate to Backups → Storage Locations → Add storage location and enter all the required
information to add a backup storage location. For details, see Prepare a storage location.

- 24/35 - Percona LLC, © 2023

 6.4.1 Create a backup schedule

6.4.1 Create a backup schedule

To create a backup schedule do the following:

1. From the main menu navigate to DBaaS → DB Cluster.

2. Click toggle in the Enable backups panel.

3. In the Backup Information panel, enter the backup details.

4. Set the schedule for when scheduled backups should take place:
From the drop-down select the Scheduled time when you want the backup to take place.

5. Click Create.

6.4.2 Restore backup

You can create a DBaaS cluster from a backup stored on S3. You can use backups from an existing cluster to spin up a new
database cluster from this backup.

- 25/35 - Percona LLC, © 2023

 6.4.2 Restore backup

To restore backup, do the following:

1. From the main menu navigate to DBaaS → DB Cluster.

2. Click toggle in the Enable restore panel.

3. Enter the information on the Enable restore panel.

4. Click Create.

Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-03-02

- 26/35 - Percona LLC, © 2023

 7. FAQ

7. FAQ

7.1 How can I contact the developers?

• Community forum.

• PMM project in JIRA.

7.2 What are the minimum system requirements?

• Server:

• Disk: 1 GB per monitored database (1 week data retention)

• Memory: 2 GB per monitored database

• CPU: Supports SSE4.2

• Client:

• Disk: 100 MB

See also

• Setting up PMM Server

• Setting up PMM Client

7.3 How can I upgrade from version 1?

There is no direct software upgrade path.

You must set up PMM 2 and connect your existing clients to it.

When all data is registered in PMM2 and expired in PMM1, decommission your PMM1 instance.

See also

• Upgrade from PMM1

• Percona blog: Running PMM1 and PMM2 Clients on the Same Host

7.4 How to control data retention?

Go to Configuration →  Settings → Advanced Settings → Data retention to adjust the value in days.

See also

Configure data retention

7.5 How are PMM Server logs rotated?

PMM Server embeds multiple components, like Victoria Metrics, Query Analytics, Grafana, managed , PostgreSQL, ClickHouse,
etc. (components). All PMM Server component logs are rotated by supervisord . The components’ log rotation settings are
stored in *.ini files within the /etc/supervisord.d directory. Those settings define both the maximum size of a log file and the
number of log files to keep. The log rotation takes place once the log file reaches its maximum size.

- 27/35 - Percona LLC, © 2023

 7.6 What privileges are required to monitor a MySQL instance?

7.6 What privileges are required to monitor a MySQL instance?

SELECT, PROCESS, SUPER, REPLICATION CLIENT, RELOAD

See also

Setting Up/Client/MySQL.

7.7 Can I monitor multiple service instances?

Yes.

You can add multiple instances of MySQL or any other service to be monitored from the same PMM Client.

To do this, you provide a unique port and IP address, or a socket for each instance, and specify a unique name for each. (If a
name is not provided, PMM uses the name of the PMM Client host.)

For example, to add MySQL monitoring for two local MySQL servers:

pmm-admin add mysql --username root --password root instance-01 127.0.0.1:3001

pmm-admin add mysql --username root --password root instance-02 127.0.0.1:3002

See also

pmm-admin add mysql

7.8 Can I rename instances?

Yes, by removing and re-adding with a different name.

When you remove a monitoring service, previously collected data remains available in Grafana. However, the metrics are tied
to the instance name. So if you add the same instance back with a different name, it will be considered a new instance with a
new set of metrics. So if you are re-adding an instance and want to keep its previous data, add it with the same name.

7.9 Can I add an AWS RDS MySQL or Aurora MySQL instance from a non-default AWS
partition?
By default, the RDS discovery works with the default aws partition. But you can switch to special regions, like the GovCloud
one, with the alternative AWS partitions (e.g. aws-us-gov ) adding them to the Settings via the PMM Server API.

- 28/35 - Percona LLC, © 2023

 7.10 What resolution is used for metrics?

To specify other than the default value, or to use several, use the JSON Array syntax: ["aws", "aws-cn"] .

7.10 What resolution is used for metrics?

The default values (in seconds):

Preset Low Medium High

Rare 300 180 60

Standard 60 10 5

Frequent 30 5 1

Custom (defaults) 60 10 5

See also

Metrics resolution

7.11 How do I set up Alerting?

When a monitored service metric reaches a defined threshold, PMM Server can trigger alerts for it using embedded Grafana
Alerting functionality.

For this, you must configure alerting rules that define conditions under which an alert should be triggered, and the contact
points used to send the alert (e.g. email).

Percona templated alerts enable you to create alerts based on built-in or custom templates to simplify the alert setup process.
Grafana managed alerts allows attaching rules to your dashboard panel and enables you to create more sophisticated alerting
rules. In addition, it can be easier to manage installations with a large number of hosts. This additional flexibility comes at
the expense of simplicity.

- 29/35 - Percona LLC, © 2023

 7.12 How do I use a custom Prometheus configuration file?

See also

Grafana Alerting

7.12 How do I use a custom Prometheus configuration file?

Normally, PMM Server fully manages the Prometheus configuration file.

However, some users may want to change the generated configuration to add additional scrape jobs, configure remote
storage, etc.

From version 2.4.0, when pmm-managed starts the Prometheus file generation process, it tries to load the /srv/prometheus/
prometheus.base.yml file first, to use it as a base for the prometheus.yml file.

The prometheus.yml file can be regenerated by restarting the PMM Server container, or by using the SetSettings API call with an
empty body.

See also

• API

• Percona blog: Extending PMM’s Prometheus Configuration

7.13 How to troubleshoot an Update?

See Troubleshoot update.

7.14 What are my login credentials when I try to connect to a Prometheus Exporter?
• User name: pmm

• Password: Agent ID

PMM protects an exporter’s output from unauthorized access by adding an authorization layer. To access an exporter, you
can use pmm as a user name and the Agent ID as a password. You can find the Agent ID corresponding to a given exporter by
running pmm-admin list .

See also

pmm-admin list

7.15 How to provision PMM Server with non-default admin password?

Currently, there is no API available to change the admin password. If you’re deploying through Docker, you can use the
following code snippet to change the password after starting the Docker container:

PMM_PASSWORD="mypassword"
echo "Waiting for PMM to initialize to set password..."
until [ "`docker inspect -f {{.State.Health.Status}} pmm-server`" = "healthy" ]; do sleep 1; done
docker exec -t pmm-server bash -c "grafana-cli --homepath /usr/share/grafana admin reset-admin-password $PMM_PASSWORD"

(This example assumes your Docker container is named pmm-server .)

- 30/35 - Percona LLC, © 2023

 7.16 How to change the PMM password for a default admin user?

7.16 How to change the PMM password for a default admin user?
If you’re deploying through Docker, you can change the default password for an admin user after starting the Docker
container as follows:

• For PMM versions 2.27.0 and later:

docker exec -t pmm-server change-admin-password <new_password>

• For PMM versions prior to 2.27.0:

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

7.17 How to use a non-default listen-port for pmm-admin?

If you configure the PMM agent to use a non-default listen-port, for pmm-admin to communicate with the agent, use the
global flag --pmm-agent-listen-port=LISTEN_PORT .

--pmm-agent-listen-port=LISTEN_PORT

Example: To use the listen-port 8000

pmm-admin --pmm-agent-listen-port=8000 add postgresql --username=pmm-agent --password=pmm-agent-password --query-source=pgstatmonitor nameofpostgres

If you are using OVF/AMI, you can change the default password through SSH by using the following command:

change-admin-password <new_password>

7.18 How PMM handles personal and confidential data

Read our Privacy Policy to learn how PMM manages personal and confidential data. More technical details can be found in
Data handling in PMM.

- 31/35 - Percona LLC, © 2023

 7.18.1 Contact us

7.18.1 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-05-22

- 32/35 - Percona LLC, © 2023

 8. Release Notes

8. Release Notes
• Percona Monitoring and Management 2.37.1
• Percona Monitoring and Management 2.37.0

• Percona Monitoring and Management 2.36.0

• Percona Monitoring and Management 2.35.0

• Percona Monitoring and Management 2.34.0

• Percona Monitoring and Management 2.33.0

• Percona Monitoring and Management 2.32.0

• Percona Monitoring and Management 2.31.0
• Percona Monitoring and Management 2.30.0

• Percona Monitoring and Management 2.29.1

• Percona Monitoring and Management 2.29.0

• Percona Monitoring and Management 2.28.0

• Percona Monitoring and Management 2.27.0

• Percona Monitoring and Management 2.26.0

• Percona Monitoring and Management 2.25.0
• Percona Monitoring and Management 2.24.0

• Percona Monitoring and Management 2.23.0

• Percona Monitoring and Management 2.22.0

• Percona Monitoring and Management 2.21.0

• Percona Monitoring and Management 2.20.0
• Percona Monitoring and Management 2.19.0
• Percona Monitoring and Management 2.18.0
• Percona Monitoring and Management 2.17.0

• Percona Monitoring and Management 2.16.0

• Percona Monitoring and Management 2.15.1
• Percona Monitoring and Management 2.15.0

• Percona Monitoring and Management 2.14.0

• Percona Monitoring and Management 2.13.0

• Percona Monitoring and Management 2.12.0

• Percona Monitoring and Management 2.11.1

• Percona Monitoring and Management 2.11.0
• Percona Monitoring and Management 2.10.1

• Percona Monitoring and Management 2.10.0

• Percona Monitoring and Management 2.9.1

• Percona Monitoring and Management 2.9.0

• Percona Monitoring and Management 2.8.0

• Percona Monitoring and Management 2.7.0

• Percona Monitoring and Management 2.6.1

• Percona Monitoring and Management 2.6.0

• Percona Monitoring and Management 2.5.0

• Percona Monitoring and Management 2.4.0

- 33/35 - Percona LLC, © 2023

 8. Release Notes

• Percona Monitoring and Management 2.3.0

• Percona Monitoring and Management 2.2.2

• Percona Monitoring and Management 2.2.1

• Percona Monitoring and Management 2.2.0

• Percona Monitoring and Management 2.1.0

• Percona Monitoring and Management 2.0.1

• Percona Monitoring and Management 2.0.0

- 34/35 - Percona LLC, © 2023

 8.0.1 Contact us

8.0.1 Contact us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-06-05

- 35/35 - Percona LLC, © 2023