Healthcheck Bundle Laravel Package

Product Decisions This Supports

• Observability & Reliability: Enables standardized health checks for Kubernetes/containerized environments, reducing MTTR (Mean Time to Recovery) by surfacing system failures early.
• DevOps Alignment: Supports CI/CD pipelines by providing /healthz endpoints for automated deployment validation (e.g., pre-rollout checks).
• Build vs. Buy: Avoids reinventing health-check logic, saving engineering time while maintaining flexibility for custom checks.
• Multi-Environment Use Cases:
  • Liveness: Detects crashes/restarts (e.g., for Kubernetes pod eviction).
  • Readiness: Validates app readiness for traffic (e.g., DB connections, cache availability).
  • Startup: Ensures critical dependencies are initialized before accepting requests.
• Compliance & SLOs: Helps meet uptime SLAs by exposing granular health metrics to monitoring tools (e.g., Prometheus).

When to Consider This Package

Adopt if:

• Your Laravel/Symfony app runs in Kubernetes or containerized environments and lacks standardized health endpoints.
• You need minimal setup for /healthz, /health/liveness, or /health/readiness without building custom middleware.
• Your team prioritizes observability but lacks dedicated SRE resources to maintain health-check infrastructure.
• You require pre-built checks (e.g., database, cache, HTTP endpoints) with configurable thresholds.

Look elsewhere if:

• Your stack is non-containerized (e.g., traditional VMs without orchestration needs).
• You need advanced health-check features (e.g., synthetic monitoring, multi-region checks) beyond basic HTTP endpoints.
• The package’s last release (2022) raises concerns about long-term maintenance (evaluate forks or alternatives like spatie/laravel-health).
• Your team prefers PHP-first solutions over Symfony bundles (this is Symfony-specific; Laravel would need a bridge like symfony/bridge).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us standardize health checks for our containerized apps with minimal effort—critical for reducing downtime in Kubernetes. It’s like a ‘health dashboard’ for our infrastructure, giving DevOps and SRE teams clear signals to act on failures before users notice. The cost? Almost zero: a Composer install and route configuration. The payoff? Faster incident response and smoother deployments."

For Engineering: "This Symfony bundle provides three key endpoints (/healthz, /liveness, /readiness) out-of-the-box, with pluggable checks for databases, caches, and external APIs. It’s lightweight, MIT-licensed, and integrates with Laravel via Symfony’s bridge. We’d save ~2–4 dev days vs. building from scratch, and it’s already battle-tested in containerized environments. Tradeoff: Limited to Symfony’s ecosystem (but we can scope this to our microservices)."