- Does Vigilance work with all Laravel queue drivers (Redis, SQS, Beanstalkd, database, sync)?
- Yes, Vigilance is fully driver-agnostic and supports database, Redis, SQS, Beanstalkd, and sync drivers. Unlike Horizon (Redis-only), it provides unified monitoring across all drivers. However, sync driver visibility is limited since jobs execute immediately without queue events.
- How do I install and set up Vigilance in a Laravel 13 project?
- Run `composer require anousss007/vigilance` and then `php artisan vigilance:install`. This publishes migrations, config, and assets. Ensure PHP 8.2+ and Laravel 12/13 are installed. Livewire 3.5+ is auto-installed as a dependency. Run migrations with `php artisan migrate`.
- Can I manually dispatch jobs or run Artisan commands from the Vigilance dashboard?
- Yes, Vigilance includes a manual control plane. Enable it by setting `VIGILANCE_CONTROL_ENABLED=true` in `.env` and configure the allowlist in `config/vigilance.php` to restrict which jobs/commands can be executed. This prevents unauthorized execution risks.
- What are the performance implications of using Vigilance in production?
- Vigilance adds minimal overhead: ~9 microseconds per APM record (deferred writes) and ~2 microseconds per trace span (off by default). The dashboard uses Livewire, which may introduce minor frontend latency for large datasets, but pagination and sampling mitigate this. Test with `VIGILANCE_SAMPLE_RATE=1` first to gauge impact.
- How does Vigilance handle storage growth, and can I limit data retention?
- Vigilance includes configurable sampling (e.g., `VigilANCE_SAMPLE_RATE=10`) and a pruning command (`php artisan vigilance:prune`). By default, it avoids unbounded storage unlike Telescope. Schedule pruning daily (e.g., retain 30 days of data) to manage growth, especially for high-volume queues.
- Does Vigilance support APM (Application Performance Monitoring) and tracing?
- Yes, Vigilance includes APM with percentiles (p50/p95/p99), Apdex scores, and error rates. Tracing is optional and adds ~2 microseconds per span. Enable it with `VIGILANCE_TRACING=true` in `.env` and test in staging first to measure storage and performance impact.
- Will Vigilance work with my existing web middleware (e.g., locale prefixes, auth redirects)?
- Vigilance inherits web middleware by default, which may conflict with locale prefixes (e.g., `/en/vigilance`) or auth redirects. Explicitly trim middleware in `app/Providers/VigilanceServiceProvider.php` using `['web' => ['except' => ['vigilance/*']]]` to avoid clashes.
- How does Vigilance compare to Laravel Telescope or Horizon for queue monitoring?
- Unlike Telescope (limited queue support) or Horizon (Redis-only), Vigilance monitors all queue drivers, tracks job lifecycle, and includes manual job dispatch and command execution. It also adds APM, RUM, and SLOs—features absent in both alternatives—while avoiding Telescope’s unbounded storage pitfalls.
- Can I integrate Vigilance with AI agents like Laravel Boost or Copilot?
- Yes, Vigilance supports AI agent integration via the MCP (Multi-Context Processing) layer. Enable it with `VIGILANCE_MCP_ENABLED=true` in `.env` to allow AI-driven debugging and analysis of job failures, traces, and logs directly from the dashboard.
- What security measures are in place to prevent unauthorized job dispatch or command execution?
- Vigilance requires double opt-in: `VIGILANCE_CONTROL_ENABLED=true` and an allowlist in `config/vigilance.php`. Additionally, dashboard access can be restricted via Laravel Gates (e.g., `viewVigilance`) or custom auth closures. Secrets in job parameters are automatically redacted to prevent exposure.