How Cronitor works

Cronitor is a monitoring service for cron jobs, workers, services, APIs and anything else that can make or receive requests. Cronitor provides observability for the jobs and backend systems that you rely on.

Monitoring a cron job

Each cron job is given a unique ping URL like{ENDPOINT} to collect information when your job starts, completes or fails. We use these telemetry pings to alert you if your job fails to run on schedule or runs for longer than expected.

We understand cron schedules and we've built a duration prediction algorithm based on past performance.
Add the ping to your crontab or your script directly. For a deeper integration use cronitor exec.
~ $ crontab -l
# m h dom mon dow   command

*/15 * * * M-F / && curl

~ $

Monitoring your entire crontab

Optionally, import your crontab in a single command and watch for updates using cronitor discover from CronitorCLI.

Heartbeat monitoring

Use heartbeats to monitor scripts, workers, agents, daemons, and other services that can't be monitored by healthcheck requests. By instrumenting your system with a simple HTTP request to the /run endpoint, we are able to alert you if your task doesn't run as expected.

Define the rules your pings will be evaluated against. You will be given a unique ping URL.
Instrument your code with Cronitor pings. Ping both /run and /complete endpoints to monitor duration.
~ $ head
from urllib2 import urlopen

# Do Everything Here



Monitor your APIs, microservices and websites using our network of global healthchecks. Watch for 200/Ok or define a healthy response using rich assertions like response body contains `success`.

Monitor server and API health with rich assertions against status code, response time and response body.
Cronitor will send healthchecks from America, Europe and Asia for cross-region verification of downtime.