PMM Query Analytics Support for EDB Postgres Advanced Server (EPAS) 17/18

1

Title: PMM Query Analytics Support for EDB Postgres Advanced Server (EPAS) 17/18

Hi Percona Team,

We are planning to integrate EDB Postgres Advanced Server (EPAS) 17/18 with PMM and would like to understand the supported options for Query Analytics (QAN).

Our questions are:

  1. Is EDB Postgres Advanced Server (EPAS) 17/18 officially supported by PMM for PostgreSQL monitoring and Query Analytics?

  2. Can PMM Query Analytics work using only the standard PostgreSQL pg_stat_statements extension on EPAS?

  3. If pg_stat_statements is supported, what are the limitations compared to using pg_stat_monitor?

  4. Is Percona’s pg_stat_monitor extension supported and compatible with EPAS 17 and EPAS 18?

  5. Does PMM support EDB’s edb_stat_monitor extension as a Query Analytics data source, or does PMM only recognize pg_stat_statements and pg_stat_monitor?

  6. If edb_stat_monitor is not supported, is there a recommended approach for achieving equivalent Query Analytics functionality on EPAS?

  7. Are there any additional extensions, configuration parameters, or known limitations when monitoring EPAS compared to PostgreSQL Community Edition?

Our primary goal is to use PMM dashboards and Query Analytics to monitor query performance, identify expensive SQL statements, analyze wait events, and perform performance troubleshooting on EPAS environments.

We would appreciate any guidance, best practices, or real-world experiences from users who have successfully integrated EPAS with PMM.

Thank you.