Uplance Monitor types Database
Monitor Postgres, MySQL and Redis
A database monitor opens a real connection and runs a real query. An open port proves almost nothing.
Free for 10 monitors · no credit card
The problem
The port is open, the process is up, the health check is green — and the database is refusing connections because it's out of connection slots, or the disk is full, or it's stuck in recovery.
This is the failure that started Uplance: a database monitor went down, and no alert was ever sent.
What the check looks at
A real connection
Postgres, MySQL or MariaDB, and Redis, authenticated the way your application authenticates.
Response time
How long the query took, with anomaly detection that learns what's normal for this hour of the week.
Encrypted credentials
Stored with AES-256-GCM at rest, never written to logs or check history.
Dependency folding
Point your API's monitor at the database as its parent, and one outage becomes one alert instead of twelve.
And the alert actually arrives
Most monitoring tools are fine until the one time the alert doesn't arrive. Uplance is built so that can't happen quietly.
- Every alert is written to an outbox before it is sent, and retried for about fifty minutes. A restart doesn't lose it.
- Once a week, a real test event is sent through every channel you've configured, and you're told which ones failed.
- If the alert pipeline is in trouble, the dashboard says so — it isn't buried in a log file.
- If the checker itself stops, the health endpoint returns 503 so an outside heartbeat can page you, and your status page says monitoring has stopped instead of showing stale green.
Common questions
- Do you need access to my production database?
- Create a user with no privileges beyond connecting. The check proves the database accepts connections and answers; it doesn't need to read your data.
- Can it reach a database on a private network?
- Not from the hosted checkers — they refuse private, loopback and cloud-metadata addresses on purpose. Run a remote agent inside your network and it performs the check there, reporting results out.
- What happens when the database goes down at 3am?
- The alert is written to an outbox before it's sent and retried for about fifty minutes, so a flaky webhook can't swallow it. An incident opens, DNS, TLS and route evidence is captured, and if nobody acknowledges within your escalation window, every admin is paged.
Also monitored
Know it's down before your customers do.
10 monitors, 30 days of history, no credit card