runitor VS Cronicle

I use runitor to send logs to healthchecks.io

Check out Healthchecks (Github, SaaS version) and runitor.

An example in bash: https://github.com/pforret/crontask There is also a standalone utility written in Go (open source, you can compile your own binary): https://github.com/bdd/runitor

Thank you! Maybe I can use it in combination with https://github.com/bdd/runitor

Yes, you have to ping healthchecks. There is a tool called runitor that makes the command a bit easier. I use this in my cron jobs to monitor web servers:

Wasn't it simpler to use Cronicle (https://github.com/jhuckaby/Cronicle)?

You can give cronicle a try. It has a web based UI and sone good stats.

Have a look at Cronicle ( https://github.com/jhuckaby/Cronicle )

Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.

Also check out http://cronicle.net/

Would recommend https://github.com/jhuckaby/Cronicle for anyone running cronjobs but would like to have an interface. It has plenty of features, logs, resource stats, and notifications. Plus it's easy to setup.

Thought I'd post here before taking a dive into this and see if anyone has any practical experience. I'm looking for centralising scheduled tasks for multiple servers, preferably with a management GUI for friendliness. I found Crontab-UI which seems to only interact with the single host's crontab. Then I stumbled upon Cronicle which looks feature rich but looks like multi-server is handled by deploying the GUI to each host. A central server + agents on each host would be nicer. I'm wondering if anyone uses Cronicle, or another solution? Thanks!