Connect MonPG

MonPG already runs an agent that collects your Postgres schema, indexes, row counts, and column statistics. dbivio reads this via the MonPG API to predict the real lock duration of migrations in your PRs.

Why MonPG is the recommended source

• ✓ No new credentials in dbivio — reuses MonPG agent collection
• ✓ Stats are always fresh (MonPG agent samples continuously)
• ✓ Multi-database setups: pick the relevant DB per repo

Setup

1. 1. Get a MonPG API key. Sign in to app.monpg.app/settings and create a Read-Only API key. Copy it.
2. 2. Open the dbivio dashboard. Go to app.dbivio.com/settings and paste the MonPG API key under Stats source.
3. 3. Map repos to databases. For each repo with a Postgres dependency, pick the corresponding MonPG database from the dropdown. dbivio uses this mapping to fetch the right stats per analysis.

Privacy

dbivio fetches catalog metadata only — table names, row count estimates, index definitions, column types. No row data, query payloads, or user information leaves MonPG. Your DB credentials never touch dbivio.

Troubleshooting

If dbivio comments show stats source: none, the API key may have expired or the database mapping might be wrong. Re-create the MonPG key and verify the repo is mapped to the right MonPG database in dbivio settings.