- What does romanzipp/laravel-queue-monitor-nova do?
- It is a Laravel Nova companion package for romanzipp/Laravel-Queue-Monitor. It registers a Nova tool that surfaces queue activity, job status, and failure metrics from the monitor's database records in the Nova admin panel. It is a presentation layer only and adds no queue listeners, workers, or monitoring infrastructure of its own.
- How do I install laravel-queue-monitor-nova?
- Install it with Composer, then register the tool in your NovaServiceProvider's tools() method. You also need romanzipp/Laravel-Queue-Monitor installed and its migrations run so the tool has data to display. No middleware or event wiring is required in application code.
- Does laravel-queue-monitor-nova require laravel-queue-monitor?
- Yes. The Nova tool reads records written by romanzipp/Laravel-Queue-Monitor, including the per-job event table and the failed-jobs table. Without the base monitor installed, configured, and actively recording job lifecycle rows, the Nova screens will show nothing useful.
- Which Laravel and Nova versions does this package support?
- Nova tools are pinned to Nova major versions through Composer constraints, and the package also depends on the base queue-monitor package's supported Laravel and PHP ranges. Check the composer.json constraints for the exact versions rather than assuming compatibility. If you are on a newer Nova major, verify it is explicitly allowed before relying on Composer leniency.
- Do I need to run extra migrations for the Nova tool?
- No. The tool does not add schema beyond what romanzipp/Laravel-Queue-Monitor migrates. You need to ensure the base package's migrations have run and that job events are being recorded before enabling the Nova UI.
- Does it work with Redis, database, or SQS queue drivers?
- Yes, the queue driver is largely irrelevant to this package because it reads monitor rows rather than inspecting the queue itself. You should still verify in staging that romanzipp/Laravel-Queue-Monitor records job lifecycle rows for your specific drivers, job classes, and dispatch paths. A monitor that silently records nothing produces a Nova screen that silently shows nothing.
- Are job payloads and exception details exposed in Nova?
- The base queue-monitor package stores serialized job payloads and exception text, which can include PII, model snapshots, or credentials embedded in job arguments. The Nova tool surfaces that data, so access must be constrained with Nova policies and, ideally, payload columns redacted. Securing and limiting that exposure is your application's responsibility, not something the package handles for you.
- Is laravel-queue-monitor-nova safe to use in production?
- Technically it is a thin, read-only admin layer, so it does not sit in the job execution path. The main risk is maintenance: the dependency chain includes commercial Nova and a single-maintainer queue-monitor package with low activity. If a new Nova major ships and the tool is not updated, you may need to patch or fork it yourself.
- Should I build my own Nova queue monitor instead of using this package?
- The package is essentially a small set of Nova Resources, filters, and a metric or two, so building an equivalent in-house is a modest effort measured in hours or a few days. Buying gives you a quick start but carries an abandonment tail and Nova version coupling. Evaluate build-versus-buy based on whether your team already maintains Nova customizations.
- How should I roll out laravel-queue-monitor-nova in staging before production?
- Install and configure romanzipp/Laravel-Queue-Monitor first in staging and confirm real jobs are producing queued, started, finished, and failed rows. Set the retention window and pruning schedule before enabling capture in production to avoid unbounded growth. Then register the Nova tool, restrict access with policies, and verify the dashboards show the expected jobs and failures.