Databases & Queues
PostgreSQL Monitoring
PostgreSQL monitoring opens a real connection and validates the startup handshake — catching auth failures, connection-limit exhaustion and wedged listeners that a TCP check alone misses.
The database answering 'accepting connections' is not the same as healthy
What it checks
- Postgres protocol handshake and accept status
- Connection latency per check
- Auth and too-many-connections failures
Set it up
- 1Add a PostgreSQL monitor with host and port
- 2Use the internal agent for private databases
- 3Alert the data owner, not just generic on-call
FAQ
How do I monitor a private Postgres instance?
Install the internal agent on a host inside the network — it runs the same check locally and reports state, no exposed port needed.
Related check types
Start monitoring in minutes
External probes plus internal agents, escalation chains and status pages — free tier, no card required.