- How do I install Statamic Vitals in a Laravel/Statamic app?
- Install it with Composer using composer require marcorieser/statamic-vitals, then let Statamic's addon manifest register the service provider. If the package ships configuration or control-panel assets, publish them with the vendor publish command and clear caches. Check the composer.json constraint first to confirm the version you install matches your Statamic major.
- Does Statamic Vitals support Statamic 6?
- Yes. The v1.3.0 release note is Add support for Statamic v6, so that version is the one to target for a Statamic 6 site. Confirm the exact Composer constraint before upgrading, because the note does not say whether v1.3.0 also supports Statamic 5 or replaces it.
- What does Statamic Vitals actually check?
- It surfaces diagnostics for your site's PHP environment, cache, storage, queues, and other vital signs in a control-panel dashboard. The checks are configurable so you can tune what is reported. The goal is to catch environment and infrastructure issues before visitors are affected.
- Is Statamic Vitals a control-panel addon or a standalone monitoring service?
- It is a Statamic addon that adds a health-check dashboard to the control panel and does not introduce a separate Node service or external daemon. The package description also mentions providing vitals for external usage, so check the README for any endpoint or export details. For most teams, the primary use is the in-CP overview.
- How do I upgrade from an older Statamic Vitals version to v1.3.0?
- Pin the package explicitly rather than floating, upgrade Statamic core to v6 first where required, then upgrade the addon. Re-publish any shipped assets and clear Stache, view, and config caches after the switch. Read the release notes and composer.json diff to confirm minimum PHP and Laravel versions.
- Can I use Statamic Vitals with Statamic 5?
- The v1.3.0 release note does not state whether Statamic 5 is still supported, so treat it as unconfirmed. If you are staying on Statamic 5, constrain the addon to the last known-good v1.2.x release. Ask the maintainer whether a v5 maintenance branch exists and what its EOL date is.
- What are the minimum PHP and Laravel versions for Statamic Vitals v1.3.0?
- The provided release information does not list them; they are defined in the package's composer.json constraints. Statamic 6 will likely raise the PHP and Laravel floor, and those floors propagate to your app. Verify the constraints with composer why-not or by inspecting the package metadata before upgrading.
- How do I test Statamic Vitals locally or in CI?
- Install it into a Statamic site that matches your target major and open the control-panel dashboard to see the checks run. In CI, include the addon in your Composer install and exercise the route or CP view with your cache, queue, and storage drivers configured. Because the checks report on environment-specific services, test with drivers that resemble production rather than only the defaults.
- What are alternatives to Statamic Vitals?
- You can use general Laravel health-check packages and external uptime monitors, or build a custom Statamic control-panel widget for your own checks. Statamic Vitals differentiates itself by being a Statamic addon with an in-CP overview and configurable vitals. If you need deep external alerting, pair it with a dedicated monitoring service.
- Is marcorieser/statamic-vitals actively maintained and safe to depend on?
- Tracking Statamic majors closely is a health signal, and v1.3.0 adds Statamic 6 support. However, a one-line release note for a major-platform-support release is thin disclosure, so review the changelog, CI matrix, and commit activity before standardizing on it. Pin versions and keep a fallback plan if maintenance lags.