Extending Percona Monitoring and Management With Custom Collectors
summary
Extends Percona Monitoring and Management by showing exactly how custom YAML custom query collector files and Prometheus-format text file collector outputs are written, where they live, and how PMM adds labels so dashboards just work. Uses Grafana + VictoriaMetrics back end, warns heavy high‑resolution queries can kill a server, and demonstrates a working text-file script that measures Postgres WAL LSN bytes to compute write rate and justify changing max_wal_size. Also covers external exporters and practical troubleshooting steps.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:15What is Percona Monitoring and Management (PMM)
- 3:56Why is Monitoring Needed?
- 8:35Extending PMM
- 11:15Custom Query Collector
- 22:12Replication Lag
- 26:15Textfile Collector
- 37:09Optimizing WAL size
- 42:44External Exporters
- 43:35Troubleshooting
related talks
51mHow to improve PostgreSQL Monitoring and ...
21mEasy way of application monitoring
30mWhy we recommend PMM to our clients
22mGetting Started with Percona Monitoring and Management
28mThe "411" on PMM
11h 43mPercona Community Live Conference - Day 1 - Open Source Databases Conference
35mBest Practices for MySQL Performance
51mCollectd and Graphite: Monitoring PostgreSQL w/Style
