Skip to content

Horizon Monitor

The Horizon monitor reads Horizon’s Redis keys directly – the same data source the Horizon dashboard uses.

What it monitors

SignalHow
Overall statusThe newest master in the masters sorted set (refreshed within the last 14 seconds), then the status field of its master:<name> hash. No fresh master means stopped
Per-supervisor stateSupervisors in the supervisors sorted set refreshed within the last 29 seconds, with each supervisor:<name> hash’s status, processes and queues
Paused stateThe master’s status is paused, or a supervisor’s status is paused
Failed jobs per minuteEntries in the failed_jobs sorted set from the last 60 seconds

Horizon stores these keys under its own Redis prefix on the horizon.connection connection.

Configuration

config/crontinel.php
'horizon' => [
'enabled' => true,
'supervisor_alert_after_seconds' => 60,
'failed_jobs_per_minute_threshold' => 5,
'connection' => 'horizon', // Redis connection used by Horizon
],

What “supervisor down” means

Crontinel compares the supervisors listed in horizon.environments for the current environment with the supervisors that are running. A configured supervisor that is not running for supervisor_alert_after_seconds is reported as down, while the master is running. Package v0.9.10 and later.

So you get an alert when the emails supervisor is gone while your default supervisor is still healthy. Supervisors are matched by name across hosts, and the check needs a cache store shared between runs (file or redis, not array).

Disabling

If you don’t use Horizon:

'horizon' => ['enabled' => false],

Queue and cron monitoring continue to work independently.