Make pg_stat_monitor the default for PMM's internal database
General
Escalation
General
Escalation
Description
PMM started to support pg_stat_monitor v2 back in v2.36.0. Since PMM’s internal PostgreSQL database is also monitored by PMM, its agent was historically configured to use pg_stat_statements for performance monitoring by default, and not the Percona-authored pg_stat_monitor.
We want to change that and configure the agent to use pg_stat_monitor by default.
No examples should be presented in QAN as they might contain sensitive data(credentials)
Solution
adjust config for new installs
migration for existing installs
How to test
Log in to PMM Server
Go to the inventory page
Confirm that the internal database query performance is monitored using pg_stat_monitor.
Check also upgrade flow from previous v3 version
How to document
None
Activity
Show:
Nurlan Moldomurov last month
Considering an option to hide internal database we decided to put this task on hold
PMM started to support
pg_stat_monitorv2 back in v2.36.0. Since PMM’s internal PostgreSQL database is also monitored by PMM, its agent was historically configured to usepg_stat_statementsfor performance monitoring by default, and not the Percona-authoredpg_stat_monitor.We want to change that and configure the agent to use
pg_stat_monitorby default.No examples should be presented in QAN as they might contain sensitive data(credentials)
Solution
adjust config for new installs
migration for existing installs