Healthchecks.io ping endpoints accept HTTP HEAD, GET and POST request methods.
When using HTTP POST, you can include an arbitrary payload in the request body. Healthchecks.io will log the first 100 kilobytes (100 000 bytes) of the request body, so that you can inspect it later.
In this example, we run
certbot renew, capture its output (both the stdout
and stderr streams), and submit the captured output to Healthchecks.io:
#!/bin/sh m=$(/usr/bin/certbot renew 2>&1) curl -fsS -m 10 --retry 5 --data-raw "$m" https://hc-ping.com/your-uuid-here
We can extend the previous example and signal either success or failure depending on the exit code:
#!/bin/sh m=$(/usr/bin/certbot renew 2>&1) curl -fsS -m 10 --retry 5 --data-raw "$m" https://hc-ping.com/your-uuid-here/$?
Runitor is a third party utility that runs the supplied command, captures its output and reports to Healthchecks.io. It also measures the execution time and retries HTTP requests on transient errors. Best of all, the syntax is simple and clean:
runitor -uuid your-uuid-here -- /usr/bin/certbot renew
While Healthchecks.io can store a small amount of logs in a pinch, it is not specifically designed for that. If you run into the issue of logs getting cut off, consider the following options:
#!/bin/sh m=$(dmesg | tail --bytes=100000) curl -fsS -m 10 --retry 5 --data-raw "$m" https://hc-ping.com/your-uuid-here