Introduction
CronBeat is a developer-friendly monitoring service that keeps your infrastructure reliable. Monitor cron jobs with heartbeat pings, or proactively check your HTTP endpoints, TCP services, and hosts — all from a single dashboard.
Two Monitoring Approaches
CronBeat offers two complementary ways to monitor your systems:
| Heartbeat Monitoring | Active Monitoring | |
|---|---|---|
| How it works | Your jobs ping CronBeat after each run | CronBeat checks your endpoints on a schedule |
| Best for | Cron jobs, scheduled tasks, background workers | Web APIs, databases, servers, network services |
| Detects | Jobs that didn't run or didn't finish | Downtime, slow responses, unexpected content |
| Monitor types | Heartbeat | HTTP, TCP, ICMP Ping |
Heartbeat Monitoring
Your cron jobs send an HTTP request (ping) to CronBeat after each successful run. If a ping is missed, you get alerted.
One line of code is all it takes. Your job pings CronBeat on success — if the ping doesn't arrive, you'll know something went wrong.
Active Monitoring
CronBeat proactively checks your endpoints at regular intervals. No code changes needed — just tell CronBeat what to monitor.
- HTTP — Monitor URLs with custom methods, headers, and validation rules
- TCP — Check if a host:port is accepting connections
- ICMP Ping — Verify a host is reachable
Multi-Channel Alerts
Get notified through the channels you already use:
- Email — Default channel, instant delivery
- Slack — Webhook integration for team channels
- Webhook — Custom HTTP callbacks for automation
- Telegram — Bot notifications for mobile (coming soon)
- WeChat — Notifications for WeChat users (coming soon)
What's Next?
Quick Start
Follow the Quick Start guide to create your first monitor in under 5 minutes.
Explore Monitoring Types
Dive deeper into Heartbeat Monitoring or Active Monitoring to understand each approach.
Set Up Alerts
Configure Alerts & Channels to get notified when things go wrong.