PMM Settings Page

PMM Settings is a special page dedicated to configuring a number of PMM options. It can be accessed through the main menu:

../_images/pmm-add-instance2.png

Choosing the PMM Settings menu entry

PMM Settings page consists of the following sections, which allow to configure different aspects of the PMM Server:

Settings

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

../_images/pmm.settings_settings1.png

Settings options

Don’t forget to click the Apply changes button to make changed options work.

Telemetry

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

Note

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 check.percona.com, which clearly explains what this service is, what it’s collecting, and how you can turn it off.

Note

The Grafana internal reporting feature is currently not managed by PMM. If you want to turn it, you need to go inside the PMM Server container and change configuration after each update.

Note

Beside using PMM Settings page, you can also disable Telemetry with the -e DISABLE_TELEMETRY=1 option in your docker run statement for the PMM Server.

SSH Key Details

This section allows you to upload your public SSH key which can be used to access the PMM Server via SSH (e.g. the PMM Server deployed as a virtual appliance).

../_images/pmm.settings_ssh_key1.png

Submitting the public key

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

AlertManager integration

This section allows you to 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 Alertmanager rules field is used to specify alerting rules in the YAML configuration format.

    ../_images/pmm.settings_alertmanager.png

    Configuring the Alertmanager integration

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

Diagnostics

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.

../_images/pmm.settings_iagnostics.png

Downloading the PMM Server logs

Table Of Contents

Previous topic

Configuring PMM Server

Next topic

Exploring PMM API