Why we recommend PMM to our clients
summary
Recommends deploying Percona Monitoring and Management for on‑prem historical monitoring using Prometheus and Grafana plus Percona Query Analytics and optional Orchestrator; supports Docker/OVA/AMI deployment. Defaults: one‑second sample rate, 30 days TSDB retention and 8 days QAN. Shows concrete wins: increasing InnoDB buffer pool from 128 MB to 3 GB drops read requests to near zero, and raising redo log size from 64 MB to 1 GB collapses write spikes. Claims lower cost and better security than SaaS.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:21Who Am I
- 2:17Agenda
- 4:40Mysqld Exporter
- 5:28Architecture Overview for Pmm
- 7:50Check Network Connectivity
- 9:04Connectivity from Your Client to the Pmm Server
- 10:20Distribution Methods
- 19:47Easy to Setup
related talks
58mBetter MySQL With Percona PMM
21mEasy way of application monitoring
22mGetting Started with Percona Monitoring and Management
28mThe "411" on PMM
50mHow To Improve PostgreSQL Monitoring and Observability With PMM - Part 2
38mAdvanced PMM Usage
51mHow to improve PostgreSQL Monitoring and ...
01h 02mHow-to MySQL Performance Diagnostic Using Percona PMM