Skip to main content

Built for load-bearing background jobs

Crontinel watches the outcome of work you already schedule: billing, sync, reporting, digests. Check in from curl, Node, Python, Sidekiq, or GitHub Actions. Laravel adds schedule attach, queue depth, and Horizon. Here are all 80 use cases.

Cron and Scheduler

Cron Heartbeat Monitoring for Laravel Schedulers

Use cron heartbeat monitoring to catch the moment schedule:run stops arriving, runs late, or silently skips a scheduled task in production.

Detect Laravel schedule:interrupt Failures After Deploy

Learn how to detect when php artisan schedule:interrupt fails to stop stale schedule:run processes after deployment, so old code does not keep running.

How to Monitor php artisan schedule:run in Production

Monitor Laravel's schedule:run command in production so you catch missed executions, slow runs, and silent scheduler failures before the missed jobs pile up.

Laravel Cron Monitoring: Scheduled Tasks and Missed Runs

Monitor every Laravel scheduled task in production so you catch missed runs, non-zero exits, and silent scheduler outages without instrumenting each task.

Monitor GitHub Actions Scheduled Workflows for Missed Runs

GitHub Actions scheduled workflows can silently stop triggering. Learn how to monitor cron workflows, detect missed runs, and alert before gaps grow.

Monitor Sidekiq Scheduled Jobs for Empty and Missed Runs

Sidekiq reports a job as processed when perform returns. Post one HTTP receipt with a record count, or a failure, from the job and register the schedule to catch missed runs.

Monitoring php artisan schedule:work in Laravel Production

Monitor Laravel's schedule:work daemon in production so you catch process crashes, memory leaks, and silent failures before your scheduled tasks stop running.

Setting Up spatie/laravel-schedule-monitor in Production

How to install, configure, and run spatie/laravel-schedule-monitor in production. Covers database setup, event listeners, missed schedules, and Crontinel.

Other

Debug a Laravel Cron Job That Fails With No Log Output

Your Laravel cron job shows FAIL but the log is empty. Find the real error, from output redirection gotchas to missing env vars and silent exceptions.

Detect When php artisan db:wipe Runs in Production

php artisan db:wipe drops every table without running migrations back. Here's how to monitor for accidental db:wipe runs and recover before downtime.

How to Monitor Laravel cache:prune-stale-tags in Production

Monitor Laravel's cache:prune-stale-tags command so stale tagged cache metadata does not build up silently when the scheduler, cache driver, or cron job fails.

How to Monitor Laravel Reverb Server in Production

Laravel Reverb is a long-lived WebSocket server that can crash without notice. Detect when Reverb goes down, set up health checks, and get alerted early.

Monitor Celery Beat Tasks That Succeed and Do Nothing

A Celery task can return SUCCESS after processing zero rows. Send one HTTP receipt per run, register the schedule, and get alerted on empty and missed runs.

Monitor node-cron Jobs That Run and Produce Nothing

node-cron runs in your process, so a crash silently stops every job. Post an HTTP receipt with a record count per run and register the schedule to catch misses.

Monitor php artisan passport:purge in Laravel Production

passport:purge cleans expired tokens, but when it fails your auth database grows unbounded. Here is how to detect purge failures before API speed drops.

Monitor sanctum:prune-expired and Fix Token Cleanup

Monitor sanctum:prune-expired in production so you catch missed cleanup runs and silent failures before expired tokens bloat your personal_access_tokens table.

Monitoring Laravel Forge Cron Jobs in Production

Laravel Forge schedules your cron entries and restarts daemons, but silent failures still slip through. Monitor Forge cron jobs and catch missed runs.

Monitoring Laravel Vapor Cron Jobs in Production

Laravel Vapor runs scheduled tasks through Lambda, not traditional cron. Here's how to monitor them, catch silent failures, and avoid Vapor's gaps.

Monitoring php artisan db:seed in Laravel Production

Detect when php artisan db:seed silently fails in production because of the --force prompt, missing autoload, or model validation errors.

Monitoring php artisan pennant:purge in Laravel Production

pennant:purge removes stale feature flag data. When it stops running, flag storage grows unbounded. Here is how to monitor it and catch failures early.

Monitoring Prometheus Metrics in Laravel Production

Laravel apps that expose Prometheus metrics often miss cron and queue failures. Pair Prometheus with targeted cron monitoring so nothing slips through.

Horizon and Workers

Detect Idle Laravel Horizon Workers Not Processing Jobs

Your Horizon dashboard shows active supervisors and workers, but jobs sit in the queue for minutes. Catch worker starvation before it becomes an incident.

horizon:purge Not Cleaning Jobs? Detect Silent Failures

horizon:purge can exit with code 0 while Redis memory keeps climbing. Here is how to tell if it is actually working and how to get alerted when it isn't.

How Laravel horizon:terminate Works and How to Monitor It

horizon:terminate only sets a Redis flag, so a deploy can race a Horizon that never stopped. How it works, where it fails silently, and how to monitor it.

Laravel Horizon Monitoring: Supervisors, Queues, Failures

Monitor Laravel Horizon in production so you catch paused supervisors, queue backlogs, and failed-job spikes without staring at the dashboard manually.

Monitor horizon:stale-process-cleanup in Production

Laravel Horizon workers can accumulate stale processes, consuming memory and blocking clean restarts. Here's how to detect when stale cleanup fails.

Monitoring horizon:continue in Laravel Production

Monitor Laravel's horizon:continue command in production with instant alerts for failures, slow execution, and unexpected exits.

Monitoring horizon:pause in Laravel Production

Monitor Laravel's horizon:pause command in production with instant alerts, failure detection, and schedule tracking to keep your Horizon queues healthy.

Monitoring horizon:work in Laravel Production

Monitor horizon:work in Laravel production with real-time alerts, failure tracking, and detailed logs to keep your queue workers running smoothly.

Scout and Telescope

Database and Migrations

Backup and Storage

Queue Monitoring

How to Monitor php artisan cache:clear Cron Job Failures

Monitor php artisan cache:clear cron jobs in production so you catch missed runs, non-zero exits, and stale cache before users see the breakage.

How to Monitor php artisan queue:failed in Production

Monitor Laravel queue:failed in production so you catch new failures, repeated job errors, and silent accumulation before users report it.

How to Monitor php artisan queue:flush in Production

Monitor Laravel's queue:flush command in production. Get alerts when failed jobs are purged unexpectedly or on an unapproved schedule.

How to Monitor php artisan queue:forget in Production

Monitor Laravel's queue:forget command in production. Get alerts when failed jobs are manually removed and their diagnostics disappear before review.

How to Monitor php artisan queue:monitor in Production

Monitor Laravel queue:monitor in production so you catch backed-up queues, QueueBusy events, and scheduler failures before the backlog turns into an incident.

How to Monitor php artisan queue:restart in Production

Monitor Laravel queue:restart in production so you catch workers that never come back, cache mismatches, and silent queue stalls after deploys.

How to Monitor php artisan queue:retry in Production

Monitor Laravel's queue:retry command in production. Get alerts when retry storms, repeated failures, or bad batches make recovery worse.

How to Monitor php artisan queue:work in Production

Monitor Laravel queue:work in production so you catch crashed workers, stale deploys, and memory leaks before your jobs start piling up.

Laravel Queue Monitoring: Depth, Failures, and Stuck Jobs

Monitor Laravel queues in production. Alert on queue depth, failed job spikes, and oldest job age before customers notice slow background processing.

Laravel Queue Worker Timeout Monitoring

Monitor Laravel queue worker timeouts, hanging jobs, and stale workers before your queue backs up. Crontinel catches timeout patterns after deploys.

Monitor Laravel Queue Processing Time and Slow Jobs

Laravel queue workers are running but jobs take longer than expected. Here's how to detect queue latency degradation before it becomes an outage.

Monitor Supervisor Queue Worker Config in Laravel

A production-ready Supervisor config for Laravel queue workers, the settings that silently break processing, and how to detect misconfigured workers.

Monitoring Failed Job Retry Loops in Laravel Horizon

A job that fails and retries forever burns queue workers without progress. Crontinel detects rising failed job rates and oldest job age spikes early.

Monitoring Redis Queue Performance in Laravel Production

Redis-backed queues degrade silently: latency creeps up, throughput drops, and jobs pile up. Here's how to detect Redis queue performance issues early.

Set Up Laravel Queue Monitoring in Production: Guide

A step-by-step guide to Laravel queue monitoring in production, from choosing a queue driver to configuring Supervisor and tracking queue depth.

Cache and Optimize

How to Monitor php artisan event:cache in Production

Monitor Laravel event:cache in production so you catch missing listeners, stale event maps, and silent registration failures before customers do.

How to Monitor php artisan model:prune in Production

Monitor Laravel model:prune in production so you catch missed pruning runs, skipped models, and silent cleanup failures before old data fills the database.

How to Monitor php artisan notifications:prune in Production

Monitor Laravel notifications:prune in production so you catch missed runs, slow executions, and silent failures before the notifications table balloons.

How to Monitor php artisan optimize in Production

Monitor Laravel's optimize command in production so you catch config cache failures, route cache problems, and bootstrap errors before they break deploys.

How to Monitor php artisan optimize:clear After Deployment

Make php artisan optimize:clear visible after Laravel deployments so stale config, route, view, and event cache problems do not survive unnoticed.

Monitoring config:cache in Laravel Production

Watch Laravel's config:cache command in production so stale environment values, broken config files, and missed deploy hooks do not quietly break your app.

Monitoring config:clear in Laravel Production

Watch Laravel's config:clear command in production so an accidentally cleared config cache, a failed rebuild, or a half-finished deploy step gets caught.

Monitoring event:clear in Laravel Production

Watch Laravel's event:clear command in production so an accidentally cleared event cache or a missed rebuild after deploy does not break event discovery.

Monitoring route:clear in Laravel Production

Watch Laravel's route:clear command in production so a cleared route cache does not leave old routes, missing endpoints, or a half-finished deployment.

Monitoring view:cache in Laravel Production

Monitor Laravel's view:cache command in production so stale compiled views, missing templates, and permission errors do not silently break your app.

Monitoring view:clear in Laravel Production

Monitor Laravel's view:clear command in production so stale compiled views from a previous release are reliably removed before the new cache is built.

routes-v7.php Explained: Laravel Route Cache Monitoring

What is bootstrap/cache/routes-v7.php? Learn how route:cache creates it, what breaks during rolling deploys, and how to get alerted when it is stale.

Alerting and Incident Response

Status Pages

Pulse

Multi-Tenant and Teams

Deploy and CI/CD

Start with one HTTP receipt

Five common runtimes post the same outcome body: curl, Node, Python, Sidekiq, and GitHub Actions. Laravel apps can add the Composer package for schedule, queue, and Horizon.

curl -X POST "$CRONTINEL_API_URL/api/v1/ingest/cron" \
  -H "Authorization: Bearer $CRONTINEL_INGEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command":"nightly-import","status":"completed","exit_code":0,"outcomes":{"metrics":{"processed_records":0}}}'