[GH-ISSUE #57] Cron output #31

New issue

Closed

opened 2026-02-25 23:40:51 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:40:51 +03:00

Owner

Originally created by @szepeviktor on GitHub (May 11, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/57

Hello!

This is a very nice project.
Have you been thinking about receiving script output?

./my-backup-script.sh > output.file 2>&1 || curl -X POST -d @output.file https://hchk.io/**************

All the best!

Originally created by @szepeviktor on GitHub (May 11, 2016). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/57 Hello! This is a very nice project. Have you been thinking about receiving script output? ``` bash ./my-backup-script.sh > output.file 2>&1 || curl -X POST -d @output.file https://hchk.io/************** ``` All the best!

kerem closed this issue

2026-02-25 23:40:51 +03:00

kerem commented

2026-02-25 23:40:52 +03:00

Author

Owner

@diwu1989 commented on GitHub (May 23, 2016):

that would mean hchk has to allocate some storage space for each ping
if you are trying to store the output, can you just pipe the output into a s3 bucket with the latest run's timestamp as the name?

s3 is a much more proper storage mechanism than relying on healthcheck to keep track of pings + store run outputs

@diwu1989 commented on GitHub (May 23, 2016): that would mean hchk has to allocate some storage space for each ping if you are trying to store the output, can you just pipe the output into a s3 bucket with the latest run's timestamp as the name? s3 is a much more proper storage mechanism than relying on healthcheck to keep track of pings + store run outputs

kerem commented

2026-02-25 23:40:53 +03:00

Author

Owner

@szepeviktor commented on GitHub (May 24, 2016):

Thank you.

@szepeviktor commented on GitHub (May 24, 2016): Thank you.

kerem commented

2026-02-25 23:40:53 +03:00

Author

Owner

@cuu508 commented on GitHub (May 24, 2016):

You can also look into hosted log aggregation services like Loggly, Papertrail, Splunk, SumoLogic.

@cuu508 commented on GitHub (May 24, 2016): You can also look into hosted log aggregation services like Loggly, Papertrail, Splunk, SumoLogic.

kerem commented

2026-02-25 23:40:53 +03:00

Author

Owner

@szepeviktor commented on GitHub (May 24, 2016):

Currently testing Papertrail...

@szepeviktor commented on GitHub (May 24, 2016): Currently testing Papertrail...

kerem referenced this issue

2026-02-25 23:43:59 +03:00

[PR #31] [MERGED] dont include tests in coverage calculation #871