laravel:horizon:metrics-and-dashboards
Horizon: Metrics and Dashboards
Make queues observable and actionable via Horizon.
Naming & Tags
- Use named queues (e.g.,
high,default,low); route jobs intentionally - Tag jobs with domain identifiers (user ID, aggregate ID) for tracing
Workers & Concurrency
- Right‑size
--max-time,--tries,--backoff - Separate critical queues into dedicated supervisors
Failures
- Use
failed()method/logging with structured context - Idempotency—ensure safe retries (unique keys, upserts, guards)
More from jpcaparas/superpowers-laravel
laravel:routes-best-practices
Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files
97laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
96laravel:quality-checks
Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided
87laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
84laravel:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest or PHPUnit; use factories, feature tests for HTTP, and parallel test runners; verify failures before implementation
83laravel:queues-and-horizon
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
83