CLI Health Check
php artisan crontinel:checkPrints a table of all monitor statuses and exits:
0– all monitors healthy1– one or more alerts active
JSON output
php artisan crontinel:check --format=jsonReturns an object with four keys:
horizon: the Horizon status, ornullwhen Horizon monitoring is offmissing_supervisors: configured Horizon supervisors that are not runningqueues: one entry per watched queuecrons: one entry per scheduled command
The exit code is the same as the table output. There is no overall status key; use the exit code.
CI/CD usage
# GitHub Actions- name: Check job health run: php artisan crontinel:check --format=json# Deploy scriptphp artisan crontinel:check || echo "Warning: monitors unhealthy after deploy"No-alert mode
By default the command also evaluates and sends local alerts. Run the check without firing alerts (useful for health endpoints):
php artisan crontinel:check --no-alertsWhat the check covers
The command reads the same three monitors as the dashboard: Horizon (running, paused, failed jobs per minute, missing supervisors), each watched queue (depth against its threshold), and the latest run of each scheduled command (exit code, late). A pipeline can print the JSON output when the exit code is 1.
crontinel:check ships with the Laravel package and needs php artisan. If your job runs in another runtime, use an HTTP check-in and register the schedule instead; the hosted app does the alerting.
Related
- Alert channels for where fired alerts are sent
- Cron monitor, queue monitor, and Horizon monitor for the thresholds behind each status
- Configuration reference for every threshold key
- Troubleshooting if the command exits
1and you do not know why