Drumbeats Documentation
Monitor cron jobs, queue workers, HTTP endpoints, and background tasks. Get alerts before users notice failures.
Drumbeats monitors cron jobs, queue workers, HTTP endpoints, and event-driven background tasks. When a job misses its schedule, fails, or hangs, Drumbeats opens an incident and alerts your team through Slack, Email, Telegram, Discord, or a webhook — before your users notice.
This is the official reference. The fastest way in: jump to the 5-minute quickstart and pick your stack.
Pick a monitor type
Drumbeats has four monitor types. Pick the one that matches what you are tracking — the rest of the docs assume you have already chosen.
| If you need to monitor… | Use this monitor | Reference |
|---|---|---|
| A scheduled job (cron / scheduler) | Cron | Cron monitors |
| A task running every N minutes (worker loop) | Heartbeat | Heartbeat monitors |
| An on-demand task (queue message, webhook, manual job) | Event-driven | Event-driven monitors |
| A public HTTP endpoint (API, website, health check) | Uptime | Uptime monitors |
Not sure which to use? Read the monitor types overview — it walks the decision tree.
Wire it into your stack
Every monitor type works with one HTTP request from your job. No SDK required.
| Stack | Guide |
|---|---|
| Node.js / TypeScript | Node.js integration |
| Python | Python integration |
| Go | Go integration |
| PHP | PHP integration |
| Shell / Bash | Shell integration |
| GitHub Actions | GitHub Actions integration |
| Kubernetes (CronJobs) | Kubernetes integration |
| AI agent (manage monitors from Claude / Cursor / VS Code) | AI agent integration |
Core reference
- Ping API — every endpoint your job calls (events, payloads, exit codes, status signals). No authentication.
- REST API — authenticated CRUD over monitors, incidents, projects, notification channels and groups.
- Notifications — channels (Slack, Email, Telegram, Discord, Webhook, Push), groups (routing), alert logic, push troubleshooting.
- Incidents — incident lifecycle, acknowledgement, resolution.
- Status pages — public health pages your customers can subscribe to.
Concepts and trade-offs
If you are evaluating Drumbeats or planning a rollout:
- How Drumbeats works — data flow from ping to alert.
- Beats and usage — how billing works.
- Alternatives — Drumbeats compared to Cronitor, Healthchecks.io, and Dead Man's Snitch.
- Security — trust center and security-relevant product behaviour.
Operating Drumbeats
- Workspace setup — onboarding, projects, members, roles, 2FA.
- Billing lifecycle — invoices, plan changes, payment failures.
- Production hardening — retries, timeouts, observability patterns.
- Support — troubleshooting steps and how to escalate.