Agentless Setup
In agentless mode, pgpulse connects directly to your Postgres instance using the credentials you provide. There is nothing to download or install.
Prerequisites
| Requirement | Detail |
|---|---|
| PostgreSQL version | 12 or later |
| Network access | Your database must be reachable from pgpulse's servers (see IP allowlist below) |
| Database user | Must have pg_monitor membership |
Create a dedicated monitoring user
CREATE USER pgpulse_monitor WITH PASSWORD 'strong-password';
GRANT pg_monitor TO pgpulse_monitor;
pgpulse makes read-only queries. No write operations are performed. Your credentials are stored encrypted at rest.
Setup Steps
1. Sign in
Go to app.pgpulse.io and sign in with GitHub or Google.
2. Add an instance
Click Add Instance and select Agentless.
3. Enter connection details
| Field | Example |
|---|---|
| Host | db.abcdefgh.supabase.co |
| Port | 5432 |
| Database | postgres |
| User | pgpulse_monitor |
| Password | strong-password |
| SSL mode | require (recommended) |
4. Save and wait
pgpulse runs a connection check immediately. If it succeeds, data starts flowing within 1–2 minutes.
Provider-Specific Notes
Supabase
Use the Direct connection string from your Supabase dashboard (Project Settings → Database → Connection string → URI). Set the user to pgpulse_monitor (or postgres if you haven't created a dedicated user yet).
Host: db.<your-project-ref>.supabase.co
Port: 5432
Database: postgres
SSLmode: require
Amazon RDS / Aurora
Make sure your RDS security group has an inbound rule allowing TCP on port 5432 from the pgpulse IP ranges below. The default postgres superuser works, but a pg_monitor user is preferred.
Neon
Use the direct connection (not pooled) from your Neon project dashboard. Pooled connections may not expose all system statistics.
Google Cloud SQL
Enable the Cloud SQL Admin API and ensure the database is not restricted to private IP only. Alternatively, use Cloud SQL Auth Proxy and the self-hosted collector.
IP Allowlist
If your database has an IP-based firewall, you'll need to allowlist the pgpulse collector IP ranges on port 5432.
To get the current list of IPs, email [email protected] with the subject line "IP Allowlist" and we'll send them over promptly.
Include your cloud provider and region in your email (e.g. "AWS us-east-1") and we can confirm which IPs apply to you specifically.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Connection test fails | Firewall blocking pgpulse | Add pgpulse IPs to your database allowlist. |
permission denied on system views | User lacks pg_monitor | Run GRANT pg_monitor TO pgpulse_monitor; |
| Dashboard shows no data after 5 min | Connection succeeded but stats are empty | Ensure pg_stat_statements is enabled for query metrics. |
| SSL error | Wrong SSL mode | Try sslmode=require or sslmode=verify-full. |