Getting Started

Add a Database — Aiven for PostgreSQL

Aiven onboarding: pg.* advanced parameters, aiven-gatekeeper extension constraints.

Aiven for PostgreSQL works fine with MonPG, with two caveats worth knowing upfront. The first is the IP allowlist (Aiven defaults to denying everyone). The second is aiven-gatekeeper, Aiven's SECURITY DEFINER guardian that blocks some extensions.

Prerequisites

Any plan tier works. Default avnadmin user (renamed if your security policy required). Public service URI exposed (the default), or VPC peering with MonPG — and if it's the latter, you'll need agent mode.

Allow MonPG IPs

Aiven service → Overview → Allowed IP addresses → Add:

20.107.185.112/29

Save. If your security model rules out IP allowlist entirely, Aiven offers VPC peering, which means agent mode for MonPG.

Connection details

Aiven console → service → Overview → Service URI. The format is:

postgres://avnadmin:<password>@<service>-<project>.aivencloud.com:<port>/defaultdb?sslmode=require

Aiven uses non-default ports — typically in the 11000-12000 range. Copy the port exactly; this catches a surprising number of people who assume 5432.

Onboard

  1. app.monpg.app → Setup → Aiven.
  2. Hosted — Auto-setup.
  3. Fill in host, port (the non-standard one), user (avnadmin), password, database, sslmode=require.
  4. Test connection → pick databases → Provision.

aiven-gatekeeper restrictions

Aiven runs a SECURITY DEFINER guardian called aiven-gatekeeper that blocks installation of extensions whose chains can grant superuser. The practical effect for MonPG:

  • pg_wait_sampling — not available.
  • hypopg — not in the default catalog.
  • auto_explain — not available.

The catalog matrix on the extensions overview page reflects this. You still get the bulk of what MonPG provides (query metrics, plan capture from logs, basic VACUUM advisor), just not the hypopg-driven Index Advisor or the auto_explain-fed plan capture pipeline.

GUCs via pg.* advanced parameters

Aiven console → service → Advanced configuration → pg.* parameters. Examples that matter for MonPG:

  • pg.log_min_duration_statement
  • pg.track_io_timing
  • pg.pg_stat_statements.max

Aiven restarts the node automatically when SPL or postmaster-context params change. The restart takes 30-60 seconds for most plan sizes; expect a brief connection blip.

Logs

Aiven offers Rsyslog, Datadog, and OpenSearch service integrations. Set one up in Aiven, then forward to MonPG via the generic webhook ingest. Or use agent mode with a local sidecar tailing logs if you have that setup already.