1
0
mirror of https://github.com/Luzifer/elastic_cron.git synced 2024-09-19 15:13:02 +00:00

Add documentation about HTTP ping

Signed-off-by: Knut Ahlers <knut@ahlers.me>
This commit is contained in:
Knut Ahlers 2017-09-13 13:25:56 +02:00
parent 64b21688ea
commit aeaaf0be28
Signed by: luzifer
GPG Key ID: DC2729FDD34BE99E

View File

@ -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 - 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 - Crons can be started on seconds, not only on minutes like a conventional cron
- Due to the logs cron jobs can get debugged - 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 ## 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 2. Generate a YAML file containing the cron definition
3. Watch your crons get executed in your log stream 3. Watch your crons get executed in your log stream
@ -26,6 +27,8 @@ jobs:
cmd: "/bin/date" cmd: "/bin/date"
args: args:
- "+%+" - "+%+"
ping_success: "https://..."
ping_failure: "https://..."
``` ```
- `rsyslog_target` - needs to be a rsyslog endpoint supporting TCP plain connections like Loggly or Papertrail does. - `rsyslog_target` - needs to be a rsyslog endpoint supporting TCP plain connections like Loggly or Papertrail does.