Configure¶
The Settings page is where you configure PMM.
Open the Settings page from the main menu with Configuration → Settings. The page opens with the Metrics Resolution settings tab selected.
On the left are the selector tabs:
- Configure
- Metrics resolution
- Advanced Settings
- Public address
- SSH Key
- Alertmanager integration
- Percona Platform
Tip
Click Apply changes to save any changes made here.
Metrics resolution¶
Metrics are collected at three intervals representing low, medium and high resolutions.
The Metrics Resolution settings tab contains a radio button with three fixed presets (Rare, Standard and Frequent) and one editable custom preset (Custom).
Each preset is a group of low, medium and high resolutions. The values are in seconds.
Time intervals and resolutions
Short time intervals are high resolution metrics. Longer time intervals are low resolution. So:
- A low resolution interval increases the time between collection, resulting in low-resolution metrics and lower disk usage.
- A high resolution interval decreases the time between collection, resulting in high-resolution metrics and higher disk usage.
The default values (in seconds) for the fixed presets and their resolution names are:
| Editable? | Preset | Low | Medium | High |
|---|---|---|---|---|
| No | Rare | 300 | 180 | 60 |
| No | Standard | 60 | 10 | 5 |
| No | Frequent | 30 | 5 | 1 |
| Yes | Custom (defaults) | 60 | 10 | 5 |
Values for the Custom preset can be entered as values, or changed with the arrows.
If there is poor network connectivity between PMM Server and PMM Client, or between PMM Client and the database server being monitored, scraping every second may not be possible when the network latency is greater than 1 second.
Advanced Settings¶
Data Retention¶
Data retention specifies how long data is stored by PMM Server. By default, time-series data is stored for 30 days. You can adjust the data retention time to balance your system’s available disk space with your metrics history requirements.
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 for each release 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.
The following information is gathered:
- PMM Server Integration Alerting feature enabled/disabled
- PMM Server Security Thread Tool feature enabled/disabled
- PMM Server Backup feature enabled/disabled
- PMM Server DBaaS feature enabled/disabled
- PMM Server Check Updates feature disabled
- Detailed information about the version of monitored MySQL services
- Monitored MongoDB services version
- Monitored PostgreSQL services version
- Total Grafana users
- Monitored nodes count
- Monitored services count
- Agents version
- Node type
We do not gather anything that identify a system, but the following two points should be mentioned:
-
The Country Code is evaluated from the submitting IP address before being discarded.
-
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 enough time to disable the service for those that do not wish to share any information.
The landing page for this service, check.percona.com, explains what this service is.
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.
Telemetry is sent straight away; 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 home page Updates dashboard if any are available.
Advisors¶
Advisors are sets of checks grouped by functionality that run a range of database health checks on a registered instance.
The findings are reported on the Advisors > Failed Checks page, and an overview is displayed on the Dashboard in the Failed Advisor Checks panel.
The Advisors option is enabled by default.
Checks are re-fetched and rerun at intervals.
See Working with Advisor checks.
Public address¶
The address or hostname PMM Server will be accessible at. Click Get from browser to have your browser detect and populate this field automatically.
DBaaS¶
Caution
DBaaS functionality is a technical preview that must be turned on with a server feature flag. See DBaaS.
Enables/disables DBaaS features on this server.
Important
Deactivating DBaaS does not suspend or remove running DB clusters.
Alerting¶
Enables Percona Alerting and reveals the Percona templated alerts option on the Alerting page.
Microsoft Azure Monitoring¶
Caution
This is a technical preview feature.
Activates Microsoft Azure monitoring.
Public Address¶
Public address for accessing DBaaS features on this server.
SSH Key¶
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.
Alertmanager integration¶
Alertmanager manages alerts, de-duplicating, grouping, and routing them to the appropriate receiver or display component.
This section lets you configure integration of VictoriaMetrics with an external Alertmanager.
Tip
If possible, use Integrated Alerting instead of 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.
Percona Platform¶
This panel is where you connect your PMM server to your Percona Platform Account.
Your Percona Platform Account is separate from your PMM User account.
Connect PMM to Percona Platform¶
To learn how to connect your PMM servers to Percona Platform and leverage Platform services that boost the monitoring capabilities of your PMM installations, see Integrate PMM with Percona Platform.
Password Reset¶
Password Forgotten¶
In case you forgot your password, click on the Forgot password link on the login page.
You will be redirected to a password reset page. Enter the email you are registered with in the field and click on Reset via Email.
An email with a link to reset your password will be sent to you.
Change Password after Login¶
If you did not forget your password but you still want to change it, go to https://okta.percona.com/enduser/settings (make sure you are logged in).
Insert you current password and the new password in the form to the bottom right of the page. If you cannot see the form, you will need to click on the Edit Profile green button (you will be prompted for you password).
Click on Change Password. If everything goes well, you will see a confirmation message.
