Hi HN, I built Cronomonitor because I kept finding out about broken cron jobs
days later, usually when a backup was needed.
It's heartbeat monitoring: each job pings a unique URL when it runs, and
Cronomonitor alerts you if a ping doesn't arrive on schedule, if the job
reports a failure, or if it runs too long. A crontab line looks like:
The $? sends the exit code, so a failed run alerts straight away instead of
waiting for the next missed one.
Things I wanted that I couldn't find in one place at this price:
- Paste the output of `crontab -l` and it creates a check per job with the same
schedules, then gives you the crontab back with the pings added
- Cron expressions in any time zone (DST-aware), or simple intervals
- Catches jobs that "succeed" but print ERROR/Traceback, using keywords you set
- Run-time tracking with /start, alerts for runs that hang or get much slower
- Alerts by email, Slack, Discord, Teams or webhook; "only after 3 failures in
a row" for flaky jobs
- Maintenance windows (one-off or weekly), monthly uptime reports, CSV export
- Copy-paste setup for systemd timers, GitHub Actions, Kubernetes CronJobs,
Laravel, Python, Node and Ruby
Pricing is flat rather than per check: Starter is £9/month for unlimited checks
and up to 5 people, Team is £29/month for 15 people, a year of history and a
REST API. There's a 14-day free trial with every feature and no card required.
Healthchecks.io is great and open source, and you should look at it too. I
wanted unlimited checks on the cheapest plan, crontab import, and output
keyword rules without self-hosting.
For launch, the first 10 people to subscribe can use code HN25 for 25% off
their first year.
I'm a solo developer in the UK and I'd really value feedback, especially on
what would stop you switching from what you use now. I'll be here all day to
answer questions.
iambenc•1h ago
It's heartbeat monitoring: each job pings a unique URL when it runs, and Cronomonitor alerts you if a ping doesn't arrive on schedule, if the job reports a failure, or if it runs too long. A crontab line looks like:
The $? sends the exit code, so a failed run alerts straight away instead of waiting for the next missed one.Things I wanted that I couldn't find in one place at this price:
- Paste the output of `crontab -l` and it creates a check per job with the same schedules, then gives you the crontab back with the pings added - Cron expressions in any time zone (DST-aware), or simple intervals - Catches jobs that "succeed" but print ERROR/Traceback, using keywords you set - Run-time tracking with /start, alerts for runs that hang or get much slower - Alerts by email, Slack, Discord, Teams or webhook; "only after 3 failures in a row" for flaky jobs - Maintenance windows (one-off or weekly), monthly uptime reports, CSV export - Copy-paste setup for systemd timers, GitHub Actions, Kubernetes CronJobs, Laravel, Python, Node and Ruby
Pricing is flat rather than per check: Starter is £9/month for unlimited checks and up to 5 people, Team is £29/month for 15 people, a year of history and a REST API. There's a 14-day free trial with every feature and no card required.
Healthchecks.io is great and open source, and you should look at it too. I wanted unlimited checks on the cheapest plan, crontab import, and output keyword rules without self-hosting.
For launch, the first 10 people to subscribe can use code HN25 for 25% off their first year.
I'm a solo developer in the UK and I'd really value feedback, especially on what would stop you switching from what you use now. I'll be here all day to answer questions.