PMM Settings Page

The PMM Settings page lets you configure a number of PMM options. It can be accessed through the main menu:



The Settings section allows you to change metrics resolution, data retention, as well as configure telemetry and automatic checking for updates:


Press Apply changes to store any changes.

Metrics resolution

Metrics are collected at three intervals representing low, medium and high resolutions. Short time intervals are regarded as high resolution metrics, while those at longer time intervals are low resolution.

The default values are:

  • Low: 60 seconds
  • Medium: 10 seconds
  • High: 5 seconds

The Metrics Resolution slider lets you choose from three preset combinations of intervals corresponding to high, medium, and low resolution (short, medium, and long collection periods).

The slider tool-tip shows the collection time corresponding to each resolution setting.

  • Setting the slider to Low increases the time between collection, resulting in low-resolution metrics (and lower disk usage).
  • Setting the slider to High decreases the time between collection, resulting in high-resolution metrics (and higher disk usage).


If there is poor network connectivity between PMM Server and PMM Client, or between PMM Client and the database server it is monitoring, scraping every second may not be possible when the network latency is greater than 1 second.


The Telemetry switch enables gathering and sending basic anonymous data to Percona, which helps us to determine where to focus the development and what is the uptake of the various versions of PMM. Specifically, gathering this information helps determine if we need to release patches to legacy versions beyond support, determining when supporting a particular version is no longer necessary, and even understanding how the frequency of release encourages or deters adoption.

Currently, only the following information is gathered:

  • PMM Version,
  • Installation Method (Docker, AMI, OVF),
  • the Server Uptime.

We do not gather anything that would make the system identifiable, but the following two things are to be mentioned:

  1. The Country Code is evaluated from the submitting IP address before it is discarded.
  2. We do create an “instance ID” - a random string generated using UUID v4. This instance ID is generated to distinguish new instances from existing ones, for figuring out instance upgrades.

The first telemetry reporting of a new PMM Server instance is delayed by 24 hours to allow sufficient time to disable the service for those that do not wish to share any information.

There is a landing page for this service, available at, which clearly explains what this service is, what it’s collecting, and how you can turn it off.

Grafana’s anonymous usage statistics is not managed by PMM. To activate it, you must change the PMM Server container configuration after each update.

As well as via the PMM Settings page, you can also disable telemetry with the -e DISABLE_TELEMETRY=1 option in your docker run statement for the PMM Server.


  1. If the Security Threat Tool is enabled in PMM Settings, Telemetry is automatically enabled.
  2. Telemetry is sent immediately; the 24-hour grace period is not honored.

Check for updates

When active, PMM will automatically check for updates and put a notification in the Updates dashboard if any are available.

Security Threat Tool

The Security Threat Tool performs a range of security-related checks on a registered instance and reports the findings.

It is disabled by default.

It can be enabled in PMM ‣ PMM Settings ‣ Settings ‣ Advanced Settings ‣ Security Threat Tool.

The checks take 24 hours to complete.

The results can be viewed in PMM ‣ PMM Database Checks.

SSH Key Details

This section lets you upload your public SSH key to access the PMM Server via SSH (for example, when accessing PMM Server as a virtual appliance).


Enter your public key in the SSH Key field and click Apply SSH Key.

Prometheus Alertmanager integration

The Prometheus Alertmanager manages alerts from Prometheus, deduplicating, grouping, and routing them to the appropriate receiver or display component.

This section lets you configure integration of Prometheus with an external Alertmanager.

  • The Alertmanager URL field should contain the URL of the Alertmanager which would serve your PMM alerts.
  • The Prometheus Alerting rules field is used to specify alerting rules in the YAML configuration format.

Fill both fields and click the Apply Alertmanager settings button to proceed.


PMM can generate a set of diagnostics data which can be examined and/or shared with Percona Support in case of some issue to solve it faster. You can get collected logs from PMM Server by clicking the Download PMM Server Logs button.


Table Of Contents

Previous topic

Configuring PMM Server

Next topic

Exploring PMM API