Scheduled job monitoring
The backup that stopped running? You find out too late.
Your cron jobs check in with LucidStack. If a ping is missing, reports a failure or arrives too late, you are alerted immediately, with the duration, exit code and job output.
Free up to 10 monitors ·No credit card ·Hosted in Europe
Nightly backup
0 3 * * * · Europe/Paris
- 12 Oct 03:00
- 4 min 12 s, exit code 0
- 13 Oct 03:00
- 4 min 30 s, exit code 0
- 14 Oct 03:00
- 4 min 08 s, exit code 0
- Next run
- 15 Oct 03:00
Cron job monitoring
Every way a job can fail
Missing, failed, too long: every case is detected.
Period or cron expression
A simple period, or the exact cron expression with its time zone and a grace period.
Start, success and failure
Start and end pings measure each run; a failure ping or a non-zero exit code opens an incident.
Maximum duration
A run that takes too long is flagged, even if it eventually succeeds.
Output saved
Job output is kept for 90 days alongside its run, so you can understand what happened.
A simple HTTP request
A curl or wget call is all it takes: copy-paste examples are provided for crontab, Bash, PHP, Laravel, Node.js and Python.
Targeted alerts
Critical jobs can alert by SMS, while others wait until morning thanks to quiet hours.
Getting started
Monitor a job in three steps
-
1
Create the heartbeat
Set the period or cron expression and the grace period.
-
2
Add the call
Paste the provided curl line at the end of your job, or at the start and end to measure duration.
-
3
Sit back
LucidStack waits for the ping; if it's missing, you get alerted.
Related pages
Start monitoring in two minutes.
Add a URL, choose where to be alerted. LucidStack takes care of the rest, day and night.