Monitoring

Know your database is up before your users do.

PostgreSQL, MySQL/MariaDB and MongoDB uptime monitoring — a real connection and a real query from our European regions, every 30 seconds to 5 minutes, with the credentials kept encrypted.

monitored databases
postgres://db.example.com:5432/orders PostgreSQL UP38ms
mysql://db-ro.example.com/shop MySQL UP21ms
mongodb://node1,node2,node3/admin MongoDB · rs0 UP64ms
Test query SELECT count(*) FROM jobs WHERE status = 'stuck' < 10 · 7 ✓

How it works.

01

Paste the connection URL

postgres://, mysql:// or mongodb:// — a replica-set seed list works too. Any user:password in it is moved to encrypted fields; the URL is stored without it.

02

Pick a query

SELECT 1 or a ping by default, or your own — a stuck-jobs count, a replication lag, a replica-set status — and the value it must return.

03

Get alerted

Connection refused, authentication failed, query timing out or a result off its threshold — the same alert channels and escalation as every other monitor.

What's included.

Three engines, one check

PostgreSQL, MySQL and MariaDB over their native protocols, MongoDB standalone or replica set (mongodb:// and mongodb+srv://), TLS on or off.

Credentials never leak

User and password are encrypted at rest and masked everywhere — API, exports, alerts, audit log, public status pages. Use a read-only user.

Query latency, not just a port

Connect + query time is recorded on every check, so a slow database shows up as a trend long before it becomes an outage.

Private databases too

A database that is not exposed to the internet is checked from a private agent running inside your network — nothing to open.