Know the moment a cron job fails
Get a push the second a cron job fails. One curl line per job, a timeline of every run, failures forwarded to Discord or Slack.
The problem
A cron throws an error in the middle of the night. The shell mails root, root forwards nowhere, and you only find out two days later when the backup is missing. Side projects don't justify a full monitoring stack just to catch this.
How Alarum solves it
Each cron POSTs success or failure to Alarum at the end of its run. Failures push to your phone, successes go quietly to the inbox, and the timeline shows every invocation. One curl line per job, no agent to install, no port to open.
Integrate in one line
Drop a curl call at the end of any cron entry. Success and failure both ping Alarum so you have one timeline per job. Replace <YOUR_TOKEN> with an ingestion token from your project, then send.
# crontab -e
*/5 * * * * /usr/local/bin/backup.sh \
&& curl -s -X POST https://alarum.me/h \
-H "Authorization: Bearer <YOUR_TOKEN>" \
-d '{"level":"success","title":"Backup ok","source":"cron"}' \
|| curl -s -X POST https://alarum.me/h \
-H "Authorization: Bearer <YOUR_TOKEN>" \
-d '{"level":"error","title":"Backup FAILED","source":"cron","tags":["backup"]}'Why teams pick Alarum for this
Instant failure alerts
When a cron POSTs an error, push lands on your phone immediately. No more "I saw the email three days later".
Run history per job
One token per cron, one timeline per token. See exactly when each invocation succeeded or failed.
Search past runs
Find every run that touched a tag, a source or a level. Full-text search across messages too.
Quiet hours
Crons that succeed at 3 AM stay silent. Errors flagged critical still cut through.
No inbound port
Your server pushes out. Nothing to expose, works behind any NAT or firewall.
Forward to Discord/Slack
Mirror failures to your team channel while keeping the success noise in Alarum.
Why not just use X?
Healthchecks.io and similar tools focus on deadman checks (alert when a ping is missed). Alarum is the inverse: your cron tells Alarum what happened, and Alarum routes failures to push, Discord or Slack. Best fit when your crons reliably get to run but you want to know fast when they fail.
Related use cases
CI/CD pipeline notifications
Push alerts for GitHub Actions, GitLab CI, Jenkins or any pipeline. Build failures, deploys and releases land in one inbox.
Read moreServer & service alert inbox
Pipe alerts from Nagios, Monit, shell checks or your own services to one mobile-friendly inbox, with a push when something breaks.
Read more