11–19 of 19 posts
The idea of sending my cronjobs to someone else to do this creeps me about (perhaps irrationally), but either way, thanks for the reminder I need to do this myself :)
Reminds me that I need to build something in Nagios to do this for my cronjobs. The idea of sending my cronjobs to someone else to do this creeps me about (perhaps irrationally), but either way, thanks for the reminder I need to do this myself :)
Hello HN. We were occasionally running into issues where our scheduled tasks would not start when expected. There were many reasons for this (environment changes, lock files not being cleaned up properly, etc). So, we created a simple application to monitor our scheduled tasks, and notify us if they didn't start or finish when expected. Now we're notified immediately (via email or SMS) when a scheduled task isn't kic…
Ultimately for me, this would replace logs and email notification that are supported pretty well out of the box with cron. It is nice to have multiple scheduled tasks consolidated with a dashboard style interface. I am confused with the selecting a timezone but all of the times being represented in UTC? Also the representation of the cron schedule (7 * * * *) which I think could be represented in a more intuitive way…
Representing the cron schedule in some other format is also feedback we have received before. I just haven't found a way to cleanly and concisely display the schedule in a format other than the cron format.
Regarding the downtime...we don't manage that right now. We're running on a single VPS. The goal of the beta is to determine if there is enough interest (and potential financial support) to deploy Proby to a more robust and fault tolerant setup.
Thanks for the feedback!
It looks pretty nice ... and adding the start and finish notifications doesn't seem too hard. But it seems to me that if Doug really meant what he said below, he would have got up, walked down the hallway and given John a real pat on the back ;)
heh, well, that's a bit harder /c most of our team is remote, but you're right. John, you get a cookie on Friday!
Very nice, but one suggestion, the 'dashboard' view might benefit from showing a sequence of graphics that show either the status of the last x number of runs: X X X ok ok ok X ok obviously color-coded to stand out, or at a minimum show the time elapsed since last successful run. This way provides a real at-a-glance way to see one or more broken tasks.
Earlier quoted context omitted.
Ultimately for me, this would replace logs and email notification that are supported pretty well out of the box with cron. It is nice to have multiple scheduled tasks consolidated with a dashboard style interface. I am confused with the selecting a timezone but all of the times being represented in UTC? Also the representation of the cron schedule (7 * * * *) which I think could be represented in a more intuitive way…
The time zone setting for the task is used to determine when Proby should be expecting a notification from that task. We're still thinking of the best way to display the times on the dashboard. Listing all of the tasks in the same time zone makes them easily sortable based on the last execution time (we could still support this sort order while displaying the tasks in their configured time zone...but it may be more c…
Looks great. Is that your own design or based on a template from Themeforest or similar? If a template, do you mind saying which one?