Cron monitoring
Cron runs jobs on a schedule. Cron monitoring checks that those jobs actually finished when you expected them to.
Why it is needed
A job can stop without anyone noticing: the server reboots, a script exits early, credentials expire, or the crontab entry is removed. The machine may still be up. The schedule still looks fine. The work did not happen.
Monitoring closes that gap. You get an alert when a run is late or missing, instead of finding out days later when a backup or report is gone.
How it works
Each monitor has a schedule and a ping URL. Your cron job requests that URL when it finishes successfully. If the ping does not arrive within the schedule plus grace, DidItCron marks the job late or down and sends an alert.
15 2 * * * /usr/local/bin/backup.sh && curl -fsS -m 10 https://diditcron.com/p/<token>
DidItCron
Free plan includes 10 monitors. Alerts go out by email by default. You can also use Slack, Discord, Teams, Telegram, PagerDuty, or a signed webhook. Same channels on every plan.