Feature

Cron job and scheduled task monitoring

A task that fails raises an error. A task that stops running raises nothing. Quiet Guard tells you when one stops checking in.

Start for free Read the documentation
On a task you already have 
->monitorHeartbeat('nightly-backup')

The problem

A scheduled task that crashes raises an exception, and you hear about it. A task that stops running raises nothing at all: the server is quiet, the logs are empty, and you find out the day somebody notices this month's invoices never went out.

What you get

  • One alert when it goes late, not one per minute of lateness
  • Silent recovery: a ping that comes back closes the incident
  • Mail, Slack or webhook, with storm protection
  • An artisan command and a curl call, for what does not run on Laravel
  • The state of every task on the project's page
  • A grace period per task, for work whose duration varies

How it works

01

A dead man's switch

Each task pings when it finishes. Past its period plus the grace you allow, it is the ABSENCE of a ping that raises the alert.

02

One line in your scheduler

A macro on a task you already have. The ping fires on success, so a task that crashes stays silent and alerts exactly as if it had never run.

03

Armed when you decide

The first ping registers the task and never alerts. You set the period once you know what it is really worth.

Start for free

No card required. Up and running in minutes.

All features