so cronic combined with a healthcheck, immediate failure alerting and integration for e.g. graylog or fluentd - would be a killer :-)
replyThanks for the suggestion!
replyThere's currently no explicit "fail" ping, as that's not the main use case I care about. It's valid, though, and I've thought about adding it.
Being able to pipe logs to curl would also be useful. I'm concerned that people might accidentally send me private/sensitive data, but I'll consider it.
> I don't see how a heartbeat alone without logs would help to identify temporary failures.
replyIt does help. Sometimes jobs unexpectedly don't run at all.
A temporary failure means that the job failed only once and then starts running again. If you want to investigate why it failed, you will need the output of that particular failed run.
reply