Weave Code
Laravel Nova Metrics Polling Laravel Package
fidum/laravel-nova-metrics-polling
Adds configurable polling to Laravel Nova metrics cards, automatically refreshing dashboards at set intervals without manual reloads. A lightweight way to keep metric values current during monitoring, demos, or live operations, with simple setup for Nova users.
Easily add polling to all your Laravel Nova metrics and cards!
Frequently asked questions about Laravel Nova Metrics Polling
- How do I install fidum/laravel-nova-metrics-polling in a Laravel app?
- Install it with Composer by running composer require fidum/laravel-nova-metrics-polling from your application root. If the package ships a configuration file, publish it with php artisan vendor:publish and select the package's provider tag. Then opt in the Nova metric cards you want refreshed on the dashboard. Check the repository README and composer.json for the exact tag and any required service provider registration for your Nova version.
- Does this package support all Laravel Nova metric cards, including value, trend, and partition metrics?
- The package is described as adding polling to Nova metric cards generally, which covers the standard value, trend, and partition metric types. Because it hooks into Nova's card rendering layer rather than your metric classes, support depends on the Nova card contract for the Nova major version you run. Confirm against the README for your Nova release before rolling it out across a dashboard.
- How do I set or change the polling interval for a Nova metric card?
- Polling is designed to be configured per metric card, so each card can specify its own refresh interval when it opts in. A published config file can supply a default interval so you do not have to repeat the value on every metric. Pick intervals that match how fast the underlying metric actually changes, since each tick triggers a request. Shorter intervals refresh faster but multiply server work on dashboards with many cards.
- Which Laravel versions does fidum/laravel-nova-metrics-polling support?
- Release 1.0.5 is documented as adding Laravel 13 support, following 1.0.4 which covered earlier Laravel releases. Because that change is most likely a widened illuminate or laravel/framework constraint, diff composer.json between the two tags to confirm the declared minimum PHP and Laravel versions. Also check whether the new constraint is stable-flagged or dev, since a pre-release Laravel 13 entry is not safe to rely on in production. Run composer why-not against your pinned versions before upgrading.
- Is polling enabled globally for the whole dashboard or per metric card?
- It is opt-in per metric card, which keeps the blast radius limited to the Nova dashboard surface. You can leave a card untouched and it will behave exactly as before, or enable polling only on the two or three metrics that need live values. That per-card approach lets you avoid unnecessary refresh traffic on expensive aggregate metrics.
- Do I need to republish assets or rebuild Nova's front-end after installing or updating?
- The 1.0.4 to 1.0.5 change is described as a compatibility-only release, which implies no asset rebuild or republish is required for that update. On first install, follow the README in case the package ships compiled JavaScript that Nova needs to serve. If you maintain a custom Nova toolchain, verify the package's assets still build against your current Nova asset pipeline before deploying.
- Will automatic metric polling add server load in production?
- Yes, each polling tick issues a request that re-runs the metric's calculation, so the cost scales with the number of polling cards multiplied by their refresh frequency. Keep intervals conservative, especially for trend or partition metrics that run aggregate queries, and consider caching the underlying data. Polling is a presentation-layer convenience, so it should never be the reason a heavy metric query runs every few seconds for every open dashboard.
- How can I test that Nova metric polling is working correctly?
- Run a dashboard smoke test on staging: confirm every polling card renders, intervals are honored, and the browser console shows no errors. Use the network panel to verify requests fire on schedule and do not overlap if a metric is slow to resolve. Leave the dashboard open for a full business cycle so you catch stale values or runaway request loops before production traffic sees them.
- Does this package require Laravel Nova, and which Nova major versions are supported?
- Yes, Laravel Nova is a hard requirement, and Nova is a paid, closed-source dependency with its own release cadence and Vue asset toolchain. That makes your real compatibility matrix PHP, Laravel, Nova, and the Node build toolchain combined, and a Laravel-only constraint bump does not settle it. Check whether the Nova constraint in composer.json was changed in the release you install, and treat Nova major upgrades as the most likely breakage point.
- Is the package maintained, and what are my alternatives if it is abandoned?
- fidum/laravel-nova-metrics-polling is a single-maintainer project, so verify the licence and confirm the repository is forkable before making it a dependency. Because it is a thin presentation-layer add-on with no persistence or domain logic, replacing it is low risk. Alternatives include writing a small custom Nova card component that calls setInterval against the metric endpoint, or another community package that provides dashboard auto-refresh.
Weaver
How can I help you explore Laravel packages today?