Observability and monitoring for Aiven for PostgreSQL®

Monitor your Aiven for PostgreSQL® service with Grafana®, Datadog, pgwatch2, and audit logging.

Choose a monitoring integration

Grafana®: Comes with a dashboard Aiven builds and maintains for you, so it's the option with the least setup. Use the reference page to see whether it already shows the metric you need before reaching for another integration.
Datadog: The right choice when your team already works in Datadog for other services and wants PostgreSQL metrics correlated with them in the same place, rather than in a separate dashboard.
pgwatch2: An open source option you run yourself, outside the Aiven ecosystem, for teams that don't want a dependency on Aiven's own dashboards or Datadog.
pgaudit logging: Unlike the other three, this isn't a metrics dashboard. It and log formats cover textual, audit-oriented records for compliance and external log tools instead.

Datadog treats PostgreSQL monitoring as separate, independently enabled pieces rather than one setting: Database Monitoring itself, relation and function metrics, and PgBouncer connection pool metrics each need their own configuration step on top of the base Datadog Metrics integration.
Beyond pg_stat_statements, Aiven for PostgreSQL also offers the pg_stat_monitor and pg_stat_plans extensions for query and execution-plan monitoring. Enabling either causes a service restart, and enabling pg_stat_monitor makes pg_stat_statements results for utility commands unreliable while it's active.
Some log_line_prefix formats include a transaction ID and query ID (txid, qid), which you can use to correlate log entries with rows in pg_stat_statements for the same query.