The SITE_NAME pinging API is used for submitting "start", "success" and "fail" signals ("pings") from the monitored systems.
All ping endpoints support:
Successful responses will have the "200 OK" HTTP response status code and a short and simple string "OK" in the response body.
HEAD|GET|POST PING_ENDPOINT{uuid}
Signals to SITE_NAME that the job has completed successfully (or, for
continuously running processes, is still running and healthy). The uuid
parameter
is unique for each check.
Example
GET /5bf66975-d4c7-4bf5-bcc8-b8d8a82ea278 HTTP/1.0
Host: hc-ping.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Jan 2020 09:58:23 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Connection: close
Access-Control-Allow-Origin: *
OK
HEAD|GET|POST PING_ENDPOINT{uuid}/fail
Signals to SITE_NAME that the job has failed. Actively signalling a failure minimizes the delay from your monitored service failing to you receiving an alert.
Example
GET /5bf66975-d4c7-4bf5-bcc8-b8d8a82ea278/fail HTTP/1.0
Host: hc-ping.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Jan 2020 09:58:23 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Connection: close
Access-Control-Allow-Origin: *
OK
HEAD|GET|POST PING_ENDPOINT{uuid}/start
Sends a "job has started!" message to SITE_NAME. This is optional but enables a few extra features:
Example
GET /5bf66975-d4c7-4bf5-bcc8-b8d8a82ea278/start HTTP/1.0
Host: hc-ping.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 29 Jan 2020 09:58:23 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Connection: close
Access-Control-Allow-Origin: *
OK