Database monitoring, from the outside
Most outages don't start at the front end — they start when a database stops accepting connections or slows to a crawl. Calmping watches your Postgres, MySQL, Redis and MongoDB the same way it watches a website: a real check, on your interval, with a failure threshold you set — so a single blip never pages you, but a real problem does.
What Calmping checks
Connectivity
The database port accepts a connection within your time limit — Postgres, MySQL, Redis, Mongo.
Latency
Connect time stays under the limit you choose, measured every interval.
Authenticated checks
Deeper probes bind an app-scoped, AES-256 encrypted secret — the credential never reaches another app.
What happens when it breaks
Calmping confirms the failure is real before it makes a sound, then opens an incident with the evidence attached, routes the alert (email, Slack, Discord, signed webhook), and — on recovery — drafts a five-field postmortem so the fix becomes memory your team can reuse next time.
Why "from the outside" matters
An external check sees what your users see. If the database is unreachable from the internet-facing path your app depends on, Calmping catches it — even when internal dashboards still look green.
Free for 1 app; Pro (€9/mo) covers up to 10 apps with encrypted database checks and AI diagnosis. Monitoring currently runs from Frankfurt.