Getting Started
What Dumza actually does
Dumza pings your HTTP or HTTPS endpoint on a schedule you set, records the response time and status code, and alerts your team the moment it starts failing. Nothing runs on your infrastructure — checks come from Dumza's own servers, so if your monitoring box would normally go down with your app, ours doesn't.
Create your first monitor
From the dashboard, click "Add Monitor" and give it a name and the URL to check. The defaults (GET request, expect a 200 status, checked every 5 minutes on the free plan) work for most sites — you only need to change them if your endpoint is unusual.
Add an alert channel
A monitor with no alert channel still tracks uptime, but nobody gets told when it goes down — you'd only find out by opening the dashboard. Add at least one channel (email is the fastest to set up) from the monitor's page so you actually hear about outages. See the Alert Channels article for webhook, Telegram and Slack setup.
What counts as "down"
A single failed check doesn't trigger an alert — that would be noisy (a transient network blip, a slow deploy). Dumza waits for a configurable number of consecutive failures (2 by default, the minimum) before opening an incident and notifying you. You can raise this per monitor if a service is known to be flaky for a few seconds at a time.
Where to go from here
Uptime Monitoring covers every check option in detail. If your endpoint needs a login token, see Authenticated Monitoring. Watching a background job instead of a URL — see Cron/Heartbeat Monitoring.