PMM works on the client/server principle, where a single server instance communicates with one or more clients.

Except when monitoring AWS RDS instances, a PMM Client must be running on the host to be monitored.

PMM context

The PMM Client package provides:

  • Exporters for each database and service type. When an exporter runs, it connects to the database or service instance, runs the metrics collection routines, and sends the results to PMM Server.
  • pmm-agent: Run as a daemon process, it starts and stops exporters when instructed.
  • vmagent: A VictoriaMetrics daemon process that sends metrics data (pushes) to PMM Server.

The PMM Server package provides:

  • pmm-managed
  • Query Analytics
  • Grafana
  • VictoriaMetrics

PMM Server


PMM Server includes the following tools:

  • Query Analytics (QAN) enables you to analyze MySQL query performance over periods of time. In addition to the client-side QAN agent, it includes the following:

    • QAN API is the back-end for storing and accessing query data collected by the QAN agent running on a PMM Client.
    • QAN Web App is a web application for visualizing collected Query Analytics data.
  • Metrics Monitor provides a historical view of metrics that are critical to a MySQL or MongoDB server instance. It includes the following:

    • VictoriaMetrics, a scalable time-series database. (Replaced Prometheus in PMM 2.12.0.)
    • ClickHouse is a third-party column-oriented database that facilitates the Query Analytics functionality.
    • Grafana is a third-party dashboard and graph builder for visualizing data aggregated (by VictoriaMetrics or Prometheus) in an intuitive web interface.
    • Percona Dashboards is a set of dashboards for Grafana developed by us.

PMM Client


The PMM Client package consist of the following:

  • pmm-admin is a command-line tool for managing PMM Client, for example, adding and removing database instances that you want to monitor. (Read more.).
  • pmm-agent is a client-side component a minimal command-line interface, which is a central entry point in charge for bringing the client functionality: it carries on client’s authentication, gets the client configuration stored on the PMM Server, manages exporters and other agents.
  • node_exporter is an exporter that collects general system metrics.
  • mysqld_exporter is an exporter that collects MySQL server metrics.
  • mongodb_exporter is an exporter that collects MongoDB server metrics.
  • postgres_exporter is an exporter that collects PostgreSQL performance metrics.
  • proxysql_exporter is an exporter that collects ProxySQL performance metrics.
  • rds_exporter is an exporter that collects Amazon RDS performance metrics.

  • azure_database_exporter is an exporter that collects Azure database performance metrics.

To make data transfer from PMM Client to PMM Server secure, all exporters are able to use SSL/TLS encrypted connections, and their communication with the PMM server is protected by the HTTP basic authentication.

  • Page updated 2021-03-31


Previous page


Next page

User Interface components

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 professional services, contact Percona Sales.