Weave Code
Nova Horizon Laravel Package
appstract/nova-horizon
Displays Laravel Horizon queue metrics inside Laravel Nova, so you can monitor workload, jobs per minute, wait times, and failed jobs from your Nova dashboard without switching tools.
appstract/nova-horizon brings Laravel Horizon monitoring into Laravel Nova. It adds a dashboard card that surfaces queue health at a glance, so you can keep an eye on background jobs without leaving the Nova admin panel.
- Displays Horizon queue metrics directly in Nova
- Highlights job throughput, wait times, and failed jobs
- Provides a quick operational health overview for queues
- Simple setup for existing Nova + Horizon applications
Frequently asked questions about Nova Horizon
- How do I install appstract/nova-horizon in a Laravel Nova application?
- Install it with composer require appstract/nova-horizon, publish the service provider, and register the tool with NovaHorizon::make() in the tools() method of app/Nova/NovaServiceProvider.php. Then run php artisan nova:publish and compile Nova assets if the package does not ship built JavaScript. You need a licensed Nova 4.x or 5.x install and Laravel Horizon backed by Redis; there are no migrations or schema changes.
- Which Laravel Nova versions does appstract/nova-horizon support?
- The package is built as a Nova tool and targets Nova 4.x and 5.x, but its compatibility matrix should be verified rather than assumed from the README. Nova's tool and card APIs have changed across major releases, and this package has a small dependent base. Run a staging spike against your exact Nova version before adopting it.
- Does appstract/nova-horizon work with Laravel Horizon 5?
- appstract/nova-horizon is a wrapper over Horizon's metric repositories, so Horizon 5 compatibility depends on whether it calls stable contracts such as MetricsRepository and JobRepository rather than raw horizon:queue:* Redis keys. Horizon moved contracts between 4.x and 5.x, so check src/NovaHorizon.php and test the rendered numbers. If it reads internal Redis keys directly, treat every Horizon upgrade as a breaking-change risk.
- Why is my Nova Horizon card blank or showing no metrics?
- A blank card is usually an asset problem: run php artisan nova:publish and rebuild assets if compiled JavaScript is not shipped. It can also mean Horizon is not installed, the queue connection is not Redis, or there is simply no sampled job activity yet. If the card renders but the numbers look wrong, suspect a Horizon repository contract mismatch instead.
- Does appstract/nova-horizon require Redis?
- Yes. Horizon stores its metrics in Redis, and this package only displays what Horizon has already sampled, so DB, SQS, or other non-Redis queues produce no data. The package adds no datastore of its own. If your queues are not Horizon-on-Redis, the package delivers no value.
- Can I restrict who sees the Horizon metrics card in Nova?
- Fine-grained authorization is not included; Nova tools inherit the coarse viewNova gate, which means every Nova user may see queue health and failed-job details. Failed-job and exception views can contain serialized payloads with customer IDs or tokens, so treat exposure as a data decision. Override a canSee() method with your own Gate if the tool exposes one, or patch the source if it does not.
- What happens to the Nova dashboard if Redis goes down?
- It should fail as an isolated card error, but the real risk is a 500 that takes down the wider Nova dashboard. The package reads Horizon data live, so Redis or Horizon being unreachable is the most likely production incident. Test Redis-down behavior in staging and decide whether to wrap the card or gate it.
- How is appstract/nova-horizon different from the /horizon dashboard?
- The /horizon route already provides the authoritative, full Horizon dashboard, including metrics and failed jobs. appstract/nova-horizon is a convenience layer that surfaces a health overview inside Nova for users who have Nova access but not Horizon or SSH access. It is not a replacement for Horizon and should be cross-checked against /horizon.
- Does appstract/nova-horizon support multiple Horizon connections, supervisors, or Redis clusters?
- The card must render every connection, supervisor, Redis cluster or sentinel setup, and environment entry you run in production; partial data leads to bad operational decisions. Support for complex topology is not guaranteed by the README, so test against your actual config/horizon.php. If it cannot cover your topology, treat that as a fork trigger rather than accepting a partial view.
- Is appstract/nova-horizon actively maintained and safe for production?
- The package has roughly 77 stars and zero dependents, so assume staleness until a compatibility spike proves otherwise. Check the last commit date, open-issue responsiveness, and the real Nova/Horizon compatibility matrix. Re-validate on every Nova or Horizon major upgrade, and cross-check displayed metrics against /horizon on a real environment before each release.
Weaver
How can I help you explore Laravel packages today?