Weave Code
Nova Log Viewer Laravel Package
laravel/nova-log-viewer
A Laravel Nova tool for viewing your application logs right inside Nova, with polling support. Install via Composer and register LogViewer::make() in your NovaServiceProvider's tools method.
A Laravel Nova tool for viewing your application logs.
Frequently asked questions about Nova Log Viewer
- How do I install laravel/nova-log-viewer in a Laravel app?
- Install it with Composer by running composer require laravel/nova-log-viewer. Then register the tool by adding \Laravel\Nova\LogViewer\LogViewer::make() to the tools() array in your application's NovaServiceProvider. No migrations, config publishing, or asset builds are required.
- Which Laravel and Nova versions does laravel/nova-log-viewer support?
- Recent releases added support for Laravel 12 and Laravel 13, along with Nova 5.7.7 and 5.9.0. The package is a Nova tool, so you must already have a licensed Nova installation before it will do anything. Check the release history for the exact compatibility matrix before upgrading either Laravel or Nova.
- Does laravel/nova-log-viewer work with an API-only or headless Laravel app?
- No. The package renders a panel inside Nova, so an application without a Nova admin panel has nowhere to attach it. API-only or headless services should look at dedicated log aggregation or CLI tooling instead. The value here is specifically putting logs in front of people who already use Nova daily.
- How does the polling feature work and can I limit how often it refreshes?
- Polling repeatedly re-reads the log file so the panel refreshes with near-real-time entries without a manual reload. The README documents no batching, pagination, or throttle controls, so there is no knob to tune if polling gets expensive on large files. Test it against production-shaped log volume in staging before rolling it out.
- Which log files can laravel/nova-log-viewer read?
- It reads conventional log files from the application's own log directory using PHP's filesystem layer. That means the standard single or daily driver writing to local disk on the same host as the Nova app is the expected setup. If logs live in stdout, external services, or a separate volume, the tool will not see them.
- Is laravel/nova-log-viewer safe to use in production?
- It is read-only by design, so the worst failure is being unable to see logs rather than corrupting application state. The real risk is disclosure: log files often contain stack traces, internal hostnames, SQL fragments, emails, and occasionally tokens. Restrict the panel to trusted Nova roles and treat that as a deliberate decision rather than an inherited default.
- Does laravel/nova-log-viewer include access control or log redaction?
- No. The package ships no role-based access control of its own and no redaction of sensitive values. It inherits whatever authorization gates already exist in your Nova installation. If compliance requires access auditing or masking of secrets in logs, this package does not provide it and you should plan accordingly.
- Will laravel/nova-log-viewer work with containerised or autoscaled deployments?
- Poorly. Each request reads only the log file on whichever replica served that request, so you may see a different, possibly empty log on every refresh. In multi-host or autoscaled setups the panel becomes misleading rather than useful. If you already centralise logs in CloudWatch, ELK, Loki, or Datadog, use that instead.
- Is laravel/nova-log-viewer actively maintained?
- Maintenance signals are strong: consecutive releases added Laravel 12, Laravel 13, and Nova 5.7.7/5.9.0 support, plus a fix so unauthenticated users are redirected instead of receiving a 403. It is a first-party Laravel package, which is the strongest adoption signal here. Community adoption, however, is thin at roughly 138 stars with few recorded dependents, so treat it as lightly battle-tested by the crowd.
- What alternatives should I consider before adding laravel/nova-log-viewer?
- For a quick look on a single box, tail -f over SSH or a tool like Laravel Pail does the job without adding a dependency. For multi-host or audited environments, a centralised platform such as CloudWatch, ELK, Loki, or Datadog is the correct answer. Choose this package only when Nova is already load-bearing and logs sit on local disk the Nova app can read.
Weaver
How can I help you explore Laravel packages today?