Skip to main content
Cron Monitoring

Know which scheduled jobs ran, failed or never started

Did last night’s backup run? Is the queue cleanup stuck? Your scheduled jobs report each run to Buggregator, and it shows which runs went fine, which failed, which never started and which never finished. Locally, without a Sentry account.

Set it up Sentry Crons or a plain ping URL
127.0.0.1:8000
Buggregator Sentry Crons tab: scheduled jobs with status, schedule, last and next run and a strip of recent runs

Sentry → Crons: every job with its status, schedule, last and next run and its last 20 runs.

Every run, and the runs that didn’t happen

Your jobs report in_progress, ok and error. Buggregator checks every 30 seconds and adds missed, timeout and unknown on its own.

📨

Two ways to report

Sentry Crons check-ins to the usual DSN, or a ping URL any script can call with curl. The first report creates the job.

🚫

Missed runs show up

The run was due and nothing came? Buggregator marks it missed. Several missed runs in a row make one entry. A job without a schedule is never marked missed.

⌛

Hung runs too

A run that started and did not finish within max_runtime (30 minutes by default) is marked timeout.

💤

Runs while Buggregator was off

A run that was due while Buggregator itself was not running is marked unknown. Needs a database file.

🚨

Needs attention first

Jobs that failed, hung, missed a run or are running late come first. One button shows only those; type to filter jobs. Times are in each job’s time zone.

📄

Output and an API

Each run keeps the output the job sent. The same data through the API: list jobs and runs, change a schedule, delete a job.

Did my backup run last night?

Wrap the backup script in three curl calls: one at the start, one when it ends fine, one when it fails. In the morning, open Sentry → Crons. A run marked ok finished fine. A failed run comes with the output the script sent. If the 2 a.m. run never called in, it is marked missed.

Setup in 60 seconds

No registration. No account. Start it and point your app at it.

1

Start Buggregator with a database file

Requires Buggregator v2.13.0 or later. The default database lives in memory, so jobs and their runs are gone after a restart: start it with -db buggregator.db or DATABASE_DSN. One file, about 40 MB, installed with one command. Prefer containers? Use the Docker tab.

$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh
$ HTTP_ADDR=127.0.0.1:8000 \
  SMTP_ADDR=127.0.0.1:1025 \
  VAR_DUMPER_ADDR=127.0.0.1:9912 \
  MONOLOG_ADDR=127.0.0.1:9913 \
  PROXY_ADDR=127.0.0.1:8080 \
  ~/.local/bin/buggregator

The script picks the file for your CPU: Intel/AMD or ARM.

One file for Linux, macOS and Windows, about 40 MB. Nothing else to install.

This run line keeps it on this computer. Without the *_ADDR settings it listens on all network interfaces →

Rather not run a script? Download the file yourself →

Runs on Windows, macOS and Linux, on Intel/AMD and ARM.

Prefer not to do it yourself? Your AI agent can set Buggregator up for you →

2

Let the job report its runs

The first report creates the job. No setup in Buggregator. Already using a Sentry SDK? Point it at Buggregator as usual and use its cron monitoring. No SDK? Call a ping URL with curl when the job starts and when it ends.

B=http://127.0.0.1:8000
curl -fsS "$B/ping/backup/start?schedule=0+2+*+*+*&tz=Europe/Berlin"
if ./backup.sh > out.log 2>&1; then
  curl -fsS -X POST --data-binary @out.log "$B/ping/backup"
else
  curl -fsS -X POST --data-binary @out.log "$B/ping/backup/fail"
fi

/ping/<job>/start: the run started. /ping/<job>: it finished fine. /ping/<job>/fail: it failed. GET or POST, no login. A POST body is kept as the run’s output (the last 10 KB). In the schedule, a + is a space.

3

Open Sentry → Crons

Every job with its status, schedule, last and next run, and its last 20 runs. Open a job for its run history and output. With no jobs yet, the tab shows how to set one up.

Works with Sentry Crons and with curl

Use the Sentry SDK you already have, or any script that can call a URL.

Sentry SDK— Crons check-ins, e.g. Laravel sentryMonitor() or Python @monitor
Sentry cron HTTP endpoint— /api/<project>/cron/<job>/<key>/
Any script— curl to /ping/<job>, /start and /fail
Schedules— crontab with 5 fields or @daily and the like; intervals from the Sentry SDK

What it does not do

  • No alerts: a missed run shows up in Buggregator, nobody is notified.
  • Runs make no cards in the event feed; they are under Sentry → Crons.
  • At most 500 jobs per project.
  • A ping sets only a crontab schedule; intervals come from the Sentry SDK. @every and TZ= inside the crontab are not supported.
  • Margin and max runtime are whole minutes. A status may appear up to 30 seconds late.

Ready to try it?

One command to start. No account needed.