Filament Spatie Laravel Health Laravel Package

Product Decisions This Supports

• Observability & Proactive Monitoring: Integrate health checks into the Filament admin panel to provide real-time visibility into system health (e.g., database connectivity, queue status, API dependencies) without requiring external tools like New Relic or Datadog.
• Developer Experience (DX) & Onboarding: Reduce context-switching for engineers by embedding health monitoring directly into the existing Filament dashboard, eliminating the need to navigate to separate CLI commands or external dashboards.
• Build vs. Buy Decision: Avoid reinventing a custom health-check UI for Filament, leveraging a battle-tested package (Spatie’s Laravel Health) with a dedicated Filament wrapper.
• Compliance & Auditing: Store health check results in the database (via Eloquent) to maintain historical records for audits, SLA reporting, or post-mortems.
• Multi-Tenancy & Feature Flags: Use the authorize method to restrict access to health checks by role/tenant, aligning with security best practices for admin panels.
• Localization & Global Teams: Support for multiple languages (e.g., Spanish, Dutch, Indonesian) to accommodate distributed teams or international deployments.
• Roadmap for Filament v5+: Future-proof the admin panel by adopting packages with active maintenance (e.g., Filament 5 support in v3.2.0).

When to Consider This Package

• Avoid if:

  • Your team already uses a dedicated observability tool (e.g., Datadog, Sentry) with deep integrations—this package is lightweight and not a replacement.
  • You require real-time alerts (e.g., Slack/PagerDuty notifications); this package focuses on UI visibility, not alerting.
  • Your application uses non-Laravel/PHP stacks (e.g., Node.js, Python).
  • You need custom metrics beyond Spatie’s predefined checks (e.g., business-specific KPIs); extend Spatie’s checks or build a custom solution.
  • Your team lacks Filament admin panel access for developers/operators (e.g., headless APIs or CLI-only deployments).

• Consider alternatives if:

  • You need historical trend analysis with visualizations (e.g., Grafana) and this package’s database storage isn’t sufficient.
  • Your infrastructure is serverless (e.g., AWS Lambda) and requires event-driven health checks.
  • You prioritize cost and already have a free tier with a third-party observability tool.

How to Pitch It (Stakeholders)

For Executives (Business/Tech Leads)

*"This package integrates proactive system health monitoring directly into our Filament admin panel, reducing downtime risks and operational overhead. By embedding Spatie’s Laravel Health checks—like database connectivity, queue processing, and environment validation—into the existing UI, our team can:

• Catch issues early before they impact users (e.g., failed cron jobs, misconfigured APIs).
• Eliminate tool sprawl by consolidating monitoring into the admin panel, saving ~2 hours/week in context-switching.
• Comply with SLAs by storing health check history in our database for audits.
• Scale globally with multi-language support for distributed teams. The MIT license and active maintenance (Filament v5 support) ensure long-term reliability with minimal upfront cost. Let’s pilot this for our [critical service] to validate the ROI."*

For Engineering Teams

*"This package lets us leverage Spatie’s battle-tested health checks with a zero-config Filament UI. Key benefits:

• 5-minute setup: Install via Composer, register checks in AppServiceProvider, and add a plugin to Filament.
• Extensible: Customize checks (e.g., add a RedisPingCheck), override UI elements (icons, labels), or restrict access via authorize().
• No vendor lock-in: Under the hood, it uses Spatie’s Laravel Health, so we can swap the UI layer (e.g., to a custom Blade view) later if needed.
• Dev-friendly: Localization support, PHP 8.5/Laravel 13 compatibility, and active community contributions. Trade-offs: Limited to PHP/Laravel; no built-in alerting (but we can pipe results to a webhook). Recommend we:

1. Start with core checks (database, queues, debug mode).
2. Add custom checks for [specific service X].
3. Store results in the DB for [use case Y]."*

For Product Managers

*"This aligns with our goals to reduce operational friction and improve reliability. Use cases:

• Post-launch monitoring: Verify new features (e.g., payment processing) don’t break existing systems.
• Incident response: Quickly triage issues during outages by checking health status in Filament.
• Onboarding: New engineers can self-serve health checks without asking for CLI access. Metrics to track:
• Reduction in mean-time-to-detect (MTTD) for critical failures.
• Developer satisfaction (survey: ‘How often do you check system health?’). Next steps: Validate with the [team] to confirm top 3 checks to prioritize (e.g., database, cache, API gateways)."*