Set Up Crons

Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job. Once implemented, it'll allow you to get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.

Requirements

Job Monitoring

Use the Laravel integration to monitor and notify you if your scheduled task is missed (or doesn't start when expected), if it fails due to a problem in the runtime (such as an error), or if it fails by exceeding its maximum runtime.

To set up, add the sentryMonitor() macro to your scheduled tasks defined in your app/Console/Kernel.php file:

app/Console/Kernel.php
Copied
protected function schedule(Schedule $schedule)
{
    $schedule->command('emails:send')
        ->everyHour()
        ->sentryMonitor('<monitor-slug>'); // add this line
}

Connecting Errors to Cron Monitors

To link any exceptions captured during your job's lifecycle, use Sentry's context with your monitor slug.

Copied
\Sentry\configureScope(function (\Sentry\State\Scope $scope): void {
    $scope->setContext('monitor', [
        'slug' => '<monitor-slug>',
    ]);
});

Alerts

When your recurring job fails to check in (missed), runs beyond its configured maximum runtime (failed), or manually reports a failure, Sentry will create an error event with a tag to your monitor.

To receive alerts about these events:

  1. Navigate to Alerts in the sidebar.
  2. Create a new alert and select "Issues" under "Errors" as the alert type.
  3. Configure your alert and define a filter match to use: The event's tags match {key} {match} {value}.

Example: The event's tags match monitor.slug equals my-monitor-slug-here

Cron completed alert filter

Learn more in Issue Alert Configuration.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").