Weave Code
Nova Server Monitor Laravel Package
insenseanalytics/nova-server-monitor
Nova Server Monitor adds a Laravel Nova dashboard card that tracks CPU, memory, disk, and load averages on your servers via a lightweight agent. View real-time metrics and history without leaving your admin panel.
A Laravel Nova tool for Spatie's Server Monitor library.
Frequently asked questions about Nova Server Monitor
- What does insenseanalytics/nova-server-monitor actually do?
- It adds a Laravel Nova dashboard card that displays server health metrics such as CPU load, memory, disk usage, network traffic, and load averages. It is a read-only presentation layer: it renders whatever spatie/laravel-server-monitor has already persisted, and it stores no data of its own. It does not run checks, collect metrics, or send alerts by itself.
- Does it support Laravel Nova 4 or Nova 5 and PHP 8?
- No. The supported window is Laravel Nova 1.x and 2.x on PHP 7.x, using Vue 2 and the Webpack asset pipeline. Nova 4 and 5 changed tool registration to Nova::script() and Nova::style() and moved to Vite with Vue 3, so Composer constraints will not resolve cleanly and the compiled bundle will not load. On a modern stack, treat it as a reference implementation rather than a dependency.
- Do I need spatie/laravel-server-monitor installed for this to work?
- Yes. This package is about thirty lines of glue around the Spatie configuration, so all real behavior such as which checks run, how often, and at what thresholds lives in laravel-server-monitor. If you install the Nova card without the collector and a working scheduler entry, you get a permanently blank or stale dashboard. Adopting the card without the underlying monitor delivers no value.
- How do I install nova-server-monitor in my Laravel application?
- Install it with Composer on a stack that resolves to Nova 1.x or 2.x on PHP 7.x, then register the card in your Nova dashboard configuration. You also need spatie/laravel-server-monitor installed and its run-checks command wired into the scheduler, otherwise the card has nothing to display. Because the package was last released in 2018, expect to budget time for CSP and mix-manifest.json issues after Composer clears.
- Does this package send alerts, notifications, or paging when a server is under load?
- No. Alerting, thresholds, and notification channels belong to spatie/laravel-server-monitor, not to this card, so tuning thresholds in the card is not possible. The card only visualizes persisted metrics. If you or your team expect paging from a page titled server monitor, fix that expectation before building anything.
- Is insenseanalytics/nova-server-monitor actively maintained and safe for production?
- No. The last release was 2018-12-08, with roughly seven years of no commits, a single maintainer, zero dependents, no tests, and no CI. There is no security response channel, so no upstream fix, including a CVE fix, will arrive. It also inherits a second upgrade problem because laravel-server-monitor itself has been superseded by spatie/laravel-health.
- Why is my Nova server monitor card blank or always green?
- The card never executes checks, so a missing or broken server-monitor run-checks scheduler entry produces a serene, permanently green dashboard with no obvious error to debug. The 2018 UI does not surface a last-checked-at timestamp, so staleness is invisible. Verify the scheduler, the underlying monitor configuration, and whether any events were actually persisted.
- Will the monitor_events table grow forever and slow down my dashboard?
- By default monitor_events is not pruned, so dashboard queries degrade on long-lived installs. You should implement a retention or pruning job if you keep it running for any length of time. Plan that maintenance from day one rather than after the card starts timing out.
- What should I use instead on Laravel 10 to 12 with Nova 4 or 5?
- Run composer show laravel/nova, and if it resolves to 4.x or 5.x, switch to a reimplementation path. The cleanest approach is a thin, self-owned Nova card over spatie/laravel-health using Health::latestResults(), reusing this package's check-to-view mapping while discarding its service provider, routes, and frontend build. Expect roughly 200 to 400 lines of work, plus options like Laravel Pulse or an external monitoring service.
- Do I need a paid Laravel Nova license to use this package?
- Yes. Nova is a commercial product at roughly 199 dollars per site plus renewals, and this MIT-licensed wrapper cannot justify that purchase on its own. It only rides a Nova license already justified elsewhere in your stack, so confirm you actually own Nova before evaluating the card.
Weaver
How can I help you explore Laravel packages today?