{% extends "base.html" %} {% load compress hc_extras humanize static %} {% block description %} {% endblock %} {% block containers %}
Make HTTP requests to the Ping URL at regular intervals. When the URL is not pinged on time, {% site_name %} will send you an alert. You can monitor any service that can make HTTP requests or send emails.
As an alternative to HTTP and HTTPS requests, you can "ping" this check by sending an email message to {{ check.email }}
A list of your checks, one for each Cron job, daemon or periodically running task you want to monitor.
Give names to your checks to easily recognize them later. 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", {% site_name %} 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 set up additional ways to get notified:
Good old email messages. | |
SMS text messages. | |
HTTP webhooks. | |
Notifications in Slack channel. | |
Instant push notifications with Pushover. | |
Instant push notifications with Pushbullet. | |
Notifications to a Telegram group or user. | |
Open and resolve incidents in PagerDuty. | |
Open and resolve incidents in PagerTree. | |
Notifications in HipChat channel. | |
Open and resolve incidents in VictorOps. | |
Notifications in Discord channel. | |
Open and resolve incidents in OpsGenie. |