Know when a cron job doesn't run.
Add two curl calls around a command in your crontab. If a run doesn't start or doesn't finish on time, CronDrive emails you or posts to Slack.
0
minute
3
hour
*
day
*
month
*
weekday
curl -fsS https://job.crondrive.com/uG2Exw/start;
tells CronDrive it started
backup.sh
your command
; curl -fsS https://job.crondrive.com/uG2Exw/end/$?
tells CronDrive it finished, with its exit code
Every run, on the record
Each job keeps a timetable of its runs: when it was due, when it started and finished, and the alerts sent when it didn't.
Nightly backup
Times in America/Santiago.
| Due | Started | Finished | Took | |
|---|---|---|---|---|
| Wed 14 Oct, 03:00 | 03:00 | 03:11 | 11 min | On time Started 03:00, finished 03:11, took 11 min. |
| Tue 13 Oct, 03:00 | Didn't run Alerts sent at 03:05 and 04:00. | |||
| Mon 12 Oct, 03:00 | 03:00 | 03:14 | 14 min | On time Started 03:00, finished 03:14, took 14 min. |
| Sun 11 Oct, 03:00 | 03:00 | 03:12 | 12 min | On time Started 03:00, finished 03:12, took 12 min. |
Set it up in three steps
-
1
Create a job
Give it the same cron expression and time zone as in your server.
-
2
Add the calls to your crontab
Copy the line from the job page; it already has your token.
-
3
Resume monitoring
Choose how long to wait before an alert. Connect Slack if your team lives there.
Free for up to 10 jobs
Email and Slack alerts included.
Sign up for freeCheck a cron expression
See what an expression means and when it runs next, in your time zone.