Monitor Laravel Queues on Any Driver with Vigilance | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ home ](https://msaied.com) [ articles ](https://msaied.com/articles) Monitor Laravel Queues, Commands, and Schedulers on Any Driver with Vigilance On this page 1. [ What Is Vigilance? ](#what-is-vigilance) 2. [ One Record Per Run, Across Every Driver ](#one-record-per-run-across-every-driver) 3. [ Manual Dispatch From Typed Forms ](#manual-dispatch-from-typed-forms) 4. [ Custom Metrics and Core Web Vitals ](#custom-metrics-and-core-web-vitals) 5. [ Installation and Securing the Dashboard ](#installation-and-securing-the-dashboard) 6. [ Beyond Queue History ](#beyond-queue-history) 7. [ Key Takeaways ](#key-takeaways) ![Monitor Laravel Queues, Commands, and Schedulers on Any Driver with Vigilance](https://cdn.msaied.com/243/78878facaaaca520b683f11457ef4785.png) [ Laravel ](https://msaied.com/articles?category=laravel) [ Composer Pacakge ](https://msaied.com/articles?category=composer-pacakge) #Laravel #Queue Monitoring #Laravel Packages #Open Source #PHP Monitor Laravel Queues, Commands, and Schedulers on Any Driver with Vigilance =============================================================================== 19 Jun 2026 4 min read ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said Table of contents 1. [ 01 What Is Vigilance? ](#what-is-vigilance) 2. [ 02 One Record Per Run, Across Every Driver ](#one-record-per-run-across-every-driver) 3. [ 03 Manual Dispatch From Typed Forms ](#manual-dispatch-from-typed-forms) 4. [ 04 Custom Metrics and Core Web Vitals ](#custom-metrics-and-core-web-vitals) 5. [ 05 Installation and Securing the Dashboard ](#installation-and-securing-the-dashboard) 6. [ 06 Beyond Queue History ](#beyond-queue-history) 7. [ 07 Key Takeaways ](#key-takeaways) What Is Vigilance? ------------------ [Vigilance](https://github.com/anousss007/laravel-vigilance) is an open-source monitoring dashboard for Laravel applications. It records queued jobs, Artisan commands, and scheduled tasks as they move through their lifecycle—from queued to running to completed or failed—capturing execution parameters, exit codes, and redacted exception traces along the way. The key differentiator: Vigilance is queue-driver agnostic. Horizon only covers Redis queues, and Telescope is aimed at local debugging. Vigilance writes a single row per run and updates it throughout the run's lifecycle, giving you one timeline regardless of whether you use database, Redis, SQS, Beanstalkd, or sync. **Requirements:** PHP 8.2+, Laravel 12 or 13, Livewire 3.5+ or 4, MIT license. --- One Record Per Run, Across Every Driver --------------------------------------- Each record stores execution parameters, final state, and a redacted exception trace when something goes wrong. Secrets are stripped automatically before storage. To keep storage costs manageable on busy queues, Vigilance samples successful runs at dispatch time while always retaining failures: ```env VIGILANCE_SAMPLE_RATE=0.1 VIGILANCE_RETENTION_DAYS=7 VIGILANCE_DB_CONNECTION=monitoring ``` Pointing `VIGILANCE_DB_CONNECTION` to a dedicated database isolates monitoring writes from your primary connection. Pruning is handled automatically based on the retention setting. --- Manual Dispatch From Typed Forms -------------------------------- When control features are enabled, Vigilance can dispatch jobs directly from the dashboard. Mark a job with the `Dispatchable` contract and Vigilance reads the constructor signature via reflection to generate a form: ```php use Vigilance\Contracts\Dispatchable; class ProcessPodcast implements ShouldQueue, Dispatchable { public static string $vigilanceLabel = 'Process a podcast'; public function __construct(public Podcast $podcast, public bool $notify = true) {} } ``` The generated form handles scalars, enums, dates, and Eloquent model binding automatically. The same mechanism lets you run allowlisted Artisan commands from the UI. Both features are off by default: ```env VIGILANCE_CONTROL_ENABLED=true ``` --- Custom Metrics and Core Web Vitals ---------------------------------- Vigilance also collects application-level data. Use the counter and gauge API from your own code: ```php use Vigilance\Vigilance; Vigilance::increment('signups'); Vigilance::gauge('cart_value', $cart->total()); ``` For frontend performance, enable Real User Monitoring (RUM) and add the Blade directive to your layout: ```env VIGILANCE_RUM=true ``` ```blade @vigilanceRum ``` This collects Core Web Vitals (LCP, INP, CLS, FCP, TTFB) from real visitors and surfaces p50, p95, and p99 latencies alongside your queue and command timelines. --- Installation and Securing the Dashboard --------------------------------------- ```bash composer require anousss007/vigilance php artisan vigilance:install php artisan migrate ``` The dashboard is local-only until you explicitly authorise access via a callback or Gate: ```php use Vigilance\Vigilance; Vigilance::auth(fn ($request) => in_array($request->user()?->email, [ 'you@example.com', ])); ``` The dashboard is available at `/vigilance` by default. --- Beyond Queue History -------------------- Vigilance includes several additional optional features: - **Issues inbox** — fingerprinted exceptions grouped across web requests, jobs, commands, and the browser - **SLO tracking** — error budgets and burn-rate alerts - **Release health** — error rate comparisons before and after a deploy - **Request and job tracing** — per-request waterfalls with N+1 detection - **Uptime checks** — availability and latency monitoring - **Log explorer** — searchable logs correlated to traces - **Alerting** — Slack, Discord, Teams, or webhook - **Worker supervisor** — fills Horizon's role for non-Redis drivers - **AI agent access** — read-only access over an MCP server --- Key Takeaways ------------- - Works with any Laravel queue driver, not just Redis - Configurable sample rate keeps storage costs low while retaining all failures - Reflection-based dispatch forms reduce the need for manual tooling - RUM and custom metrics bring frontend and business data into the same dashboard - All sensitive data is redacted before storage - MIT-licensed and self-hosted Source: [Laravel News — Monitor Laravel Queues, Commands, and Schedulers on Any Driver with Vigilance](https://laravel-news.com/monitor-laravel-queues-commands-and-schedulers-on-any-driver-with-vigilance) Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Fmonitor-laravel-queues-commands-and-schedulers-on-any-driver-with-vigilance&text=Monitor+Laravel+Queues%2C+Commands%2C+and+Schedulers+on+Any+Driver+with+Vigilance) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Fmonitor-laravel-queues-commands-and-schedulers-on-any-driver-with-vigilance) Frequently Asked Questions ---------------------------- 3 questions Q01 How is Vigilance different from Laravel Horizon and Telescope? Horizon only monitors Redis-backed queues, and Telescope is designed for local debugging. Vigilance works with any queue driver—database, Redis, SQS, Beanstalkd, and sync—and is built for production use, writing a single record per run updated throughout its lifecycle. Q02 How does Vigilance handle storage costs on high-throughput queues? Vigilance samples successful runs at dispatch time using a configurable sample rate (e.g., VIGILANCE_SAMPLE_RATE=0.1 keeps 10% of successes) while always retaining failed runs. You can also point it to a separate database connection and set a retention period for automatic pruning. Q03 Can Vigilance dispatch jobs and run Artisan commands from the dashboard? Yes, when VIGILANCE_CONTROL_ENABLED=true is set, Vigilance uses reflection to read a job's constructor signature and generates a typed form for dispatching it. The same mechanism supports running allowlisted Artisan commands from the UI. Both features are off by default. Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![Laravel AI SDK: Tool-Calling Agents and Conversation Persistence](https://cdn.msaied.com/260/8c84f424e42da01993c9ba4b8eb19655.png) laravel ai agents ### Laravel AI SDK: Tool-Calling Agents and Conversation Persistence Build reliable tool-calling AI agents in Laravel using the Prism package. Learn how to wire tools, persist con... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 21 Jun 2026 3 min read Read ](https://msaied.com/articles/laravel-ai-sdk-tool-calling-agents-and-conversation-persistence) [ ![Laravel Livewire v3 Internals: Morph Markers, JS Hooks, and Alpine Integration](https://cdn.msaied.com/259/e8ce445f021c2b26ebe4dd5da50014f8.png) livewire laravel alpine ### Laravel Livewire v3 Internals: Morph Markers, JS Hooks, and Alpine Integration Go beyond the docs: understand how Livewire v3 diffs the DOM with morph markers, intercept the lifecycle with... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 21 Jun 2026 3 min read Read ](https://msaied.com/articles/laravel-livewire-v3-internals-morph-markers-js-hooks-and-alpine-integration) [ ![Laravel Package Development: Service Providers, Auto-Discovery, and Config Merging](https://cdn.msaied.com/258/673a80fa8e42ae375a4bba21bdcd92ea.png) laravel packages service-providers ### Laravel Package Development: Service Providers, Auto-Discovery, and Config Merging Build a production-ready Laravel package from scratch — covering service provider design, auto-discovery via c... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 21 Jun 2026 3 min read Read ](https://msaied.com/articles/laravel-package-development-service-providers-auto-discovery-and-config-merging-1) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://msaied.com) - [Projects](https://msaied.com/projects) - [Articles](https://msaied.com/articles) - [Certificates](https://msaied.com/certificates) - [Contact](https://msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)