From aeaaf0be28cc26149294ee6777c4616652fd4030 Mon Sep 17 00:00:00 2001 From: Knut Ahlers Date: Wed, 13 Sep 2017 13:25:56 +0200 Subject: [PATCH] Add documentation about HTTP ping Signed-off-by: Knut Ahlers --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5cf2cc2..7606682 100644 --- a/README.md +++ b/README.md @@ -7,10 +7,11 @@ This project is a quick and dirty replacement for running a cron daemon inside d - It logs the output of the jobs into a remote syslog target (like Papertrail) using TCP syslog - Crons can be started on seconds, not only on minutes like a conventional cron - Due to the logs cron jobs can get debugged +- On success and failure a HTTP ping to [Healthchecks](https://healthchecks.io/) or [Cronitor](https://cronitor.io/) can be executed ## Usage -1. Put the [binary](https://gobuilder.me/get/github.com/Luzifer/rsyslog_cron/rsyslog_cron_master_linux-amd64) into your container +1. Put the [binary](https://github.com/Luzifer/rsyslog_cron/releases/latest) into your container 2. Generate a YAML file containing the cron definition 3. Watch your crons get executed in your log stream @@ -26,6 +27,8 @@ jobs: cmd: "/bin/date" args: - "+%+" + ping_success: "https://..." + ping_failure: "https://..." ``` - `rsyslog_target` - needs to be a rsyslog endpoint supporting TCP plain connections like Loggly or Papertrail does.