Built Cronitorex to stop losing track of failing cron jobs, now looking for feedback
I run cron jobs and scheduled tasks across a few servers, and the recurring problem was always the same. A job silently stops running (bad deploy, disk full, wrong permissions after a server rebuild) and nobody notices until something ownstream breaks days later.
I looked at existing monitoring tools and kept hitting the same trade-off: either narrow (just cron pings, no uptime checks) or heavier than I wanted. So I built Cronitorex. Wrap a job with a ping call to track start/success/failure, or point it at a URL for scheduled HTTP/SSL checks, and get alerted the moment something goes quiet.
It's free to use right now, no paid plan yet. Mainly looking for feedback from people who actually run cron jobs or scheduled tasks in production: what wouldmake this a tool you'd switch to, and what's missing?
