Data Monitoring / PostgreSQL Monitoring
PostgreSQL: Statement statistics coverage
A query performance dashboard is empty on a new PostgreSQL host. Check whether pg_stat_statements is installed and configured for the intended collection scope.
Environment and inputs: PostgreSQL 18 documentation baseline; views, extensions and permissions vary across versions and managed services.
Failure scenario
A query performance dashboard is empty on a new PostgreSQL host. Confirm the cause before choosing a fix.
Evidence to collect
Check whether pg_stat_statements is installed and configured for the intended collection scope. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Enable the supported extension configuration through change control and verify actual captured statements. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for statement statistics coverage using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.