Statamic Health Laravel Package

Product Decisions This Supports

• Proactive Monitoring & Reliability: Integrate health checks into Statamic-based CMS projects to preemptively identify infrastructure or application issues (e.g., disk space, database connections, queue backlogs) before they impact users. Aligns with reliability-driven development (RDD) and SRE principles.
• DevOps/Platform Team Enablement: Reduce operational overhead by automating health monitoring for self-hosted Statamic instances, especially for agencies or enterprises managing multiple client sites. Supports internal tooling for MSPs (Managed Service Providers).
• Build vs. Buy: Avoid reinventing health-check infrastructure for Statamic; leverage this lightweight, maintainable package instead of custom scripts or third-party SaaS tools (e.g., Datadog, New Relic) for simple use cases.
• Compliance & Auditing: Demonstrate uptime and system health for clients requiring SLAs or regulatory compliance (e.g., healthcare, finance) by logging and alerting on critical failures.
• Feature Roadmap: Phase 1: Basic health checks (disk, DB, queues). Phase 2: Extend with custom checks (e.g., API latency, third-party service dependencies). Phase 3: Integrate with existing monitoring dashboards (Grafana, Statamic admin panel).

When to Consider This Package

• Adopt if:

  • Your team manages self-hosted Statamic instances and lacks centralized monitoring.
  • You need lightweight, PHP-native health checks without external dependencies (e.g., no Prometheus/Blackbox Exporter).
  • Your use case is Statamic-specific (e.g., CMS asset storage, database connections, or queue workers).
  • You want to send alerts via Statamic’s notification system (e.g., email, Slack) without complex setup.
  • Your team prioritizes simplicity over granularity (e.g., no need for distributed tracing or APM features).

• Look elsewhere if:

  • You require enterprise-grade monitoring (e.g., real-time dashboards, historical trend analysis) → Use Laravel Scout + Grafana or Statamic + New Relic.
  • Your stack includes non-PHP services (e.g., Node.js, Python) → Use Prometheus + Alertmanager.
  • You need synthetic monitoring (e.g., uptime checks from external locations) → Use UptimeRobot or Better Stack.
  • Your team lacks PHP/Laravel expertise to customize checks → Consider low-code tools like StatusCake or Pingdom.
  • The package’s last release (2022) is a concern for long-term maintenance → Evaluate Spatie’s other active packages or Laravel’s built-in laravel-debugbar.

How to Pitch It (Stakeholders)

For Executives/Business Leaders:

"This package lets us automate health monitoring for our Statamic-powered sites—catching issues like full disk space or database timeouts before they disrupt clients. For example, if a client’s site hits 90% disk usage, we’ll get an alert to intervene, reducing downtime and support tickets. It’s a low-cost, high-impact way to improve reliability, especially for our self-hosted projects. Think of it as ‘set-and-forget’ insurance for our infrastructure."

ROI:

• Reduces unplanned downtime → higher client satisfaction.
• Lowers DevOps overhead → faster response to critical issues.
• Future-proofs for compliance/audits → trust with enterprise clients.

For Engineering/Technical Stakeholders:

*"Spatie’s statamic-health provides a battle-tested, Laravel-native way to add health checks to Statamic projects with minimal setup. It’s ideal for:

• Quick wins: Plug-and-play checks for disk space, DB connections, queues (like Laravel’s queue:failed).
• Extensibility: Add custom checks (e.g., HTTP ping to third-party APIs, Statamic asset storage limits) via PHP.
• Integration: Alerts trigger via Statamic’s notification system (e.g., Slack, email) or can be hooked into existing tools.

Why not build? It’s MIT-licensed, actively maintained by Spatie (a trusted Laravel vendor), and avoids reinventing wheel for basic monitoring. For advanced use cases, we can layer it with Laravel Horizon or Prometheus later."*

Trade-offs:

• Pros: Lightweight, PHP-first, no external services.
• Cons: Limited to Statamic/Laravel; no built-in dashboards (but can export data to Grafana).