Make HTTP requests to the Ping URL at regular intervals. When the URL is not pinged on time, Healthchecks will send you an alert. You can monitor any service that can make HTTP requests or send emails.
https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076
# m h dom mon dow command
8 6 * * * /home/user/backup.sh && curl -fsS -m 10 --retry 5 -o /dev/null https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076
# using curl (10 second timeout, retry up to 5 times):
curl -m 10 --retry 5 https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076
# using wget (10 second timeout, retry up to 5 times):
wget https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076 -T 10 -t 5 -O /dev/null
# Using Python 3 standard library:
import socket
import urllib.request
try:
urllib.request.urlopen("https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076", timeout=10)
except socket.error as e:
# Log ping failure here...
print("Ping failed: %s" % e)
# Using the requests library:
import requests
try:
requests.get("https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076", timeout=10)
except requests.RequestException as e:
# Log ping failure here...
print("Ping failed: %s" % e)
require 'net/http'
require 'uri'
Net::HTTP.get(URI.parse('https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076'))
var https = require('https');
https.get('https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076').on('error', (err) => {
console.log('Ping failed: ' + err)
});
package main
import "fmt"
import "net/http"
import "time"
func main() {
var client = &http.Client{
Timeout: 10 * time.Second,
}
_, err := client.Head("https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076")
if err != nil {
fmt.Printf("%s", err)
}
}
file_get_contents('https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076');
using (var client = new System.Net.WebClient())
{
client.DownloadString("https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076");
}
// the server returns appropriate CORS headers so cross-domain AJAX requests work:
var xhr = new XMLHttpRequest();
xhr.open('GET', 'https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076', true);
xhr.send(null);
# inside a PowerShell script:
Invoke-RestMethod https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076
# Without an underlying script, passing the command to PowerShell directly:
powershell.exe -command &{Invoke-RestMethod https://hc.stg.oceanx.org/ping/96dd81cc-f394-4761-b6cf-cfdd05720076}
As an alternative to HTTP requests, you can also report "liveness" by sending email messages.
You can instruct Healthchecks to look for a particular keyword in the subject line. This is handy when your backup software sends an email after every run, and uses a different subject line depending on success or failure.
A list of your checks, one for each Cron job, daemon or scheduled task you want to monitor.
Give names and assign tags to your checks to easily recognize them later.
Tap on the integration icons to toggle them on and off.
Adjust Period and Grace time to match the periodicity and duration of your tasks.
New. A check that has been created, but has not received any pings yet. | |
Up. Time since last ping has not exceeded Period. | |
Late. Time since last ping has exceeded Period, but has not yet exceeded Period + Grace. | |
Down. Time since last ping has exceeded Period + Grace. When check goes from "Late" to "Down", Healthchecks sends you a notification. |
Alternatively, you can define the expected ping dates and times using a cron expression. See Cron Syntax Cheatsheet for the supported syntax features.
Grace Time specifies how "late" a ping can be before you will be alerted. Set it to be a little above the expected duration of your cron job.
You can add a longer, free-form description to each check. Leave notes and pointers for yourself and for your team.
You can also see the log of received pings and sent "Down" notifications.
Healthchecks provides status badges for each of the tags you have used. Additionally, the "Healthchecks" badge shows the overall status of all checks in your account.
The badges have public, but hard-to-guess URLs. You can use them in your READMEs, dashboards or status pages.
Healthchecks monitoring is a great fit for cron jobs and cron-like systems (systemd timers, Jenkins build jobs, Windows Scheduled Tasks, wp-cron, uwsgi cron-like interface, Heroku Scheduler, ...). A failed cron job often has no immediate visible consequences, and can go unnoticed for a long time.
Specific examples:
Healthchecks monitoring can be used for lightweight server monitoring: ensuring a particular system service, or the server as a whole is alive and healthy. Write a shell script that checks for a specific condition, and pings Healthchecks if successful. Run the shell script regularly.
Specific examples: