Heartbeat Monitoring
Your cron job sends a simple HTTP ping when it completes; CloudStats alerts you if the expected ping doesn't arrive.
The scariest failures are the quiet ones
A web server crashing is obvious. A backup script that's been failing silently for three weeks is not — until you need that backup. CloudStats' heartbeat monitoring for cron jobs closes that gap: your script pings CloudStats when it runs, and if that ping doesn't arrive on schedule, you get alerted.
Runtime Alerts
Get notified if a job runs significantly longer than usual, a common early sign something's wrong.
Grace Periods
Set flexible grace periods for jobs that don't run on a perfectly fixed schedule.
Failure History
See a timeline of every run, success, and failure — useful when debugging an intermittent issue.
1. Add one line to your cron job that pings a unique CloudStats URL on completion.
2. Tell CloudStats the expected schedule and an acceptable grace period.
3. If the ping doesn't arrive on time, you're alerted automatically.
FAQ
Frequently asked questions
How does cron monitoring work without installing anything special?
You add a single curl command to the end of your existing cron job that pings a unique URL — no agent or library required.
Can it monitor jobs that don't run on a fixed schedule?
Yes, you can configure flexible windows and grace periods for irregular schedules.
What if my job usually takes 2 minutes but suddenly takes 20?
You can set a maximum expected runtime and get alerted when a job overruns it, even if it eventually finishes.