{% extends "base.html" %} {% load compress hc_extras humanize static %} {% block description %} {% endblock %} {% block containers %}

Monitoring for your nightly backups, weekly reports, cron jobs and background tasks.

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.

{% site_name %} creates unique Ping URLs like this one:

{% include "front/snippets/crontab.html" %}
{% include "front/snippets/bash_curl.html" %} {% include "front/snippets/bash_wget.html" %}
{% include "front/snippets/python_urllib2.html" %} {% include "front/snippets/python_requests.html" %}
{% include "front/snippets/ruby.html" %}
{% include "front/snippets/node.html" %}
{% include "front/snippets/php.html" %}
{% include "front/snippets/cs.html" %}
{% include "front/snippets/browser.html" %}
{% include "front/snippets/powershell.html" %} {% include "front/snippets/powershell_inline.html" %}

As an alternative to HTTP and HTTPS requests, you can "ping" this check by sending an email message to {{ check.email }}

{% if registration_open %}

{% site_name %} monitors the heartbeat messages sent by your cron jobs, services and APIs. Get immediate alerts you when they don't arrive on schedule.

Sign Up – It's Free
{% endif %}

A quick peek of what's inside:

My Checks page

A list of your checks, one for each Cron job, daemon or periodically running 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.

Period/Grace Time dialog
Each check has configurable Period and Grace Time parameters. Depending on these parameters and time since the last ping, the check is in one of the following states:
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.
Cron dialog

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.

Details Page

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.

Details Page

{% site_name %} provides status badges for each of the tags you have used. Additionally, the "{% site_name %}" 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.

Integrations
Set up additional ways to get notified:

Email icon

Email
 

{% if enable_sms %}
SMS icon

SMS
 

{% endif %}
Webhook icon

Webhooks
 

Slack icon

Slack
Chat

{% if enable_telegram %}
Telegram icon

Telegram
Chat

{% endif %} {% if enable_pushover %}
Pushover icon

Pushover
Push Notifications

{% endif %} {% if enable_pushbullet %}
Pushbullet icon

Pushbullet
Push Notifications

{% endif %} {% if enable_pd %}
PagerDuty icon

PagerDuty
Incident Management

{% endif %}
HipChat icon

HipChat
Chat

VictorOps icon

VictorOps
Incident Management

{% if enable_discord %}
Discord icon

Discord
Chat

{% endif %}
OpsGenie icon

OpsGenie
Incident Management

PagerTree icon

PagerTree
Incident Management

{% if enable_trello %}
Trello icon

Trello
Project Management

{% endif %}

What Can I Monitor With {% site_name %}?

Cron Jobs

{% site_name %} 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:

  • Filesystem backups
  • Database backups
  • Daily, weekly, monthly report emails
  • SSL renewals
  • Business data import and sync
  • Antivirus scans
  • Dynamic DNS updates

Processes, Services, Servers

{% site_name %} 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 {% site_name %} if successful. Run the shell script regularly.

Specific examples:

  • Check a specific docker container is running
  • Check a specific application process is running
  • Check database replication lag
  • Check system resources: free disk, free RAM, ...
  • Send simple, unconditional "I'm alive" messages from your server (or your NAS, router, Raspberry Pi, ...)
{% if registration_open %}

{% site_name %} is a free and open source service. Setting up monitoring for your cron jobs only takes minutes. Start sleeping better at nights!

Sign Up
{% endif %}
{% include "front/signup_modal.html" %} {% endblock %} {% block scripts %} {% compress js %} {% endcompress %} {% endblock %}