- What does llaski/nova-server-metrics do?
- It is a Laravel Nova dashboard card that displays live host-level server metrics: CPU load, memory usage, and disk usage. It is a thin PHP metric provider plus a compiled Vue component registered through NovaServiceProvider::cards(). It has no migrations, models, queue workers, or external service dependencies, and it is intended as an at-a-glance admin convenience rather than a monitoring system of record.
- How do I install llaski/nova-server-metrics in Laravel Nova?
- Install it with Composer using composer require llaski/nova-server-metrics:^1.2, then register the card in NovaServiceProvider::cards() and publish the package assets. There are no migrations or config file changes anticipated. Realistic effort is a few hours including verification, not days.
- Does llaski/nova-server-metrics support Laravel Nova 4?
- Yes, version 1.2.0 is the release that adds Nova 4 support. The assessment notes that this Nova 4 compatibility change is the entire substance of the 1.2.0 release. Check the package composer.json constraint before upgrading to confirm whether it widens support to Nova 3 and 4 or requires Nova 4 only.
- Is llaski/nova-server-metrics compatible with Laravel Nova 3?
- Earlier releases, likely 1.1.0, were effectively Nova 3-only according to the assessment. If 1.2.0 replaced the Nova constraint with Nova 4 only, applications still on Nova 3 must stay pinned at 1.1.0 and will stop receiving updates. That becomes a fork-or-replace decision rather than a routine upgrade.
- How does llaski/nova-server-metrics collect CPU, memory, and disk metrics?
- The collection mechanism is not reviewed in the provided assessment; it may use /proc, PHP built-ins, or exec and shell_exec calls. That distinction materially affects deployment risk on locked-down or managed hosts where process execution is disabled. Review the source and test behavior before relying on it in production.
- Will llaski/nova-server-metrics work when exec or shell_exec is disabled?
- The overview does not confirm whether the card degrades gracefully when exec is disabled or /proc is unreadable. Test it in a local or staging environment with process execution disabled and as a low-privilege user. Confirm how the card behaves before promoting it to production.
- Does llaski/nova-server-metrics cache metrics or run on every dashboard load?
- No caching is described in the provided assessment; the card appears to execute its collection routine when the dashboard card renders. Confirm this in the source if you expect high-traffic admin dashboards. The package has no queue workers or external dependencies to offload collection.
- Who can see server metrics with llaski/nova-server-metrics?
- Host resource metrics are visible to anyone with access to the Nova dashboard where the card is registered. The data is low sensitivity, but you should confirm it is not exposed to lower-privileged Nova roles. Use Nova role and permission controls if access needs to be restricted.
- Does llaski/nova-server-metrics support multiple servers or clusters?
- The package is a Nova card that reads host-level resource data and appears to be strictly single-host. Multi-node or cluster metrics are not described as in scope. For fleet-wide monitoring, use a dedicated monitoring system rather than this dashboard convenience.
- Is llaski/nova-server-metrics actively maintained and safe for production?
- It has a single author, three tagged releases, five merged PRs, no visible CI matrix, and no visible security policy or contributing guide, so the bus factor is one. It is a leaf dependency, which makes adoption and removal cheap and reversible. For production, pin the exact version, verify reported values against tools like free, df, and uptime, and re-verify the card whenever you upgrade Nova.