Monitor, record, organize your cron jobs and scheduled tasks. Receive alerts when they fail.

Sign Up Log In

What is CronAlarm?

As developers and system administrators, some of the most important things we do are executed as cron jobs and scheduled tasks. However, too often we do not have adequate insight into the performance and overall health of our jobs. CronAlarm solves this problem by providing a set of easy-to-use APIs that you call as a part of your workflow. By doing so we'll be able to keep you informed of any problems.

Easy To Use

If your cron job can access a URL, you can use CronAlarm. It's simple and easy.

Robust Monitoring

CronAlarm will watch for jobs that run too quick, run too long, or don't run at the correct interval. You can also report your own errors.

Custom Alerts

You can receive alerts in various ways including email, webhooks, and Slack.


Results from jobs run across various servers, applications, and locations are all stored in the same place.


Group your jobs into applications so you can view/monitor related jobs together.


We'll keep the results of your jobs for up to 1 year so you can see performance trends and success/failure rates for individual jobs over time.

Simple API

You do a basic GET request to a URL at the beginning and end of your job. From that we'll know how long it took to run and what time it ran. We'll do the rest from there.

Advanced API

Allows you to report the name or IP address of the server from which the job ran, the path to the file, your own success/failure status, and your own message to be recorded with the results.

Informative Dashboard

Quick and easy view showing all results from the last 24 hours as well as the current status of all jobs.

How It Works

You'll begin by telling CronAlarm about your jobs. This includes, optionally telling CronAlarm how often the job should run and how long it should take to execute. You will then be given an API key specific for your job. To begin monitoring your jobs, you simply wrap your code with a beginning and end API call. For the Simple API it looks like this for a job with an API key of 12345:

//do your stuff here...
With just these 2 lines of code, we'll be able to tell when and how long your job ran.

The Advanced API is, well, more advanced. But it's still super easy, and provides some nice features that help when issues arise. You start off by doing a simple GET request just like the Simple API. You follow with a POST request that can send additonal information:

//do your stuff here...
curl -X POST -H 'Content-type: application/json' --data '{"success": "0", "server": "webserver1", "path": "/var/www/ftptransfer.js", "message": "failure to connect to remote server"}'
Getting an error report that tells you that your file transfer job failed is nice, but getting an error report that tells you that your file transfer job on server 'webserver1' located at '/var/www/ftptransfer.js' is pretty cool and much more helpful. If you manage jobs that run on multiple servers you'll really appreciate this additional information.

Keep in mind we are using curl just as an example. Most likely you will be using another language such as Java, Perl, etc. that have built-in tools for accessing URLs. But if curl is your thing, it's all right with us.

View Complete Documentation

Get Started With A 7-Day Free Trial
No Credit Card Needed

10 Jobs
Simple API
Email Notifications
100 Jobs
Simple & Advanced API
Email Notifications
Custom Webhooks
Slack Integration
500 Jobs
Simple & Advanced API
Email Notifications
Custom Webhooks
Slack Integration

 Sign Up