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, CSV2 Process Monitoring will send you an alert. You can monitor any service that can make HTTP requests or send emails.

For each of your periodic tasks, CSV2 Process Monitoring provides an unique URL similar to this one:

https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330

# m h dom mon dow command
  8 6 *   *   *   /home/user/backup.sh && curl -fsS -m 10 --retry 5 -o /dev/null https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330

# using curl (10 second timeout, retry up to 5 times):
curl -m 10 --retry 5 https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330

# using wget (10 second timeout, retry up to 5 times):
wget https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330 -T 10 -t 5 -O /dev/null

# Using Python 3 standard library:
import socket
import urllib.request

try:
    urllib.request.urlopen("https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330", 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://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330", 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://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330'))

var https = require('https');
https.get('https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330').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://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330")
    if err != nil {
        fmt.Printf("%s", err)
    }
}

file_get_contents('https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330');

using (var client = new System.Net.WebClient())
{
       client.DownloadString("https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330");
}

// the server returns appropriate CORS headers so cross-domain AJAX requests work:
var xhr = new XMLHttpRequest();
xhr.open('GET', 'https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330', true);
xhr.send(null);

# inside a PowerShell script:
Invoke-RestMethod https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330

# Without an underlying script, passing the command to PowerShell directly:
powershell.exe -command &{Invoke-RestMethod https://healthcheck.competiscan.com/ping/51168094-73b0-459e-a8b8-2f894896f330}

As an alternative to HTTP requests, you can also report "liveness" by sending email messages.

You can instruct CSV2 Process Monitoring 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 quick peek of what's inside:

Live-updating Dashboard

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.

Simple Configuration

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. The time since the last ping has not exceeded Period.
	Late. The time since the last ping has exceeded Period, but has not yet exceeded Period + Grace.
	Down. The time since the last ping has exceeded Period + Grace. When a check goes from "Late" to "Down", CSV2 Process Monitoring sends you a notification.

Cron Expression Support

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 are alerted. You should set it to be a little above the expected duration of your cron job.

Details and Event Log

You can add a longer, free-form description to each check. Leave notes and pointers for yourself and your team.

You can also see the log of received pings and sent "Down" notifications.

Public Status Badges

CSV2 Process Monitoring provides status badges for each of the tags you have used. Additionally, the "CSV2 Process Monitoring" 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 multiple ways to get notified:

Webhooks

Slack
Chat

Mattermost
Chat

Microsoft Teams
Chat

OpsGenie
Incident Management

PagerDuty
Incident Management

PagerTree
Incident Management

Prometheus
Event Monitoring

Spike.sh
Incident Management

Splunk On-Call
Incident Management

Zulip
Chat

What Can I Monitor With CSV2 Process Monitoring?

Cron Jobs

CSV2 Process Monitoring 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

You can use CSV2 Process Monitoring for lightweight server monitoring: ensuring a particular system service or the whole server is alive and healthy. Write a shell script that checks for a specific condition, and pings CSV2 Process Monitoring if successful. Run the shell script regularly.