- What is pragmarx/health used for?
- PragmaRX Health is a Laravel package for monitoring application health through configurable checks for services such as the database, cache, storage, and queues. It exposes health results via a route and can notify you when checks fail. It is best treated as a legacy health panel rather than a modern observability or orchestration tool.
- Is pragmarx/health compatible with Laravel 10, Laravel 11, and PHP 8?
- There is no reliable evidence that pragmarx/health supports Laravel 10, Laravel 11, or PHP 8, and its last release was in 2019. Its Composer constraints and framework integrations are likely limited to older Laravel and PHP versions. Run a dependency audit and a CI test against your exact production runtime before considering it.
- How do I install and configure pragmarx/health?
- Installation starts with composer require pragmarx/health in a compatible legacy project, followed by publishing and editing the package configuration and exposing its health route as described in the README. Because the package is effectively unmaintained, confirm that Composer resolution, service provider registration, and route middleware behave correctly in an isolated staging environment. Wrap the integration behind an internal service interface if you need a temporary stopgap.
- Does pragmarx/health support Kubernetes liveness and readiness probes?
- pragmarx/health was not designed for Kubernetes liveness or readiness probes, structured health APIs, or multi-service aggregation. It provides a Laravel route that reports configured application checks, which is not the same as a lightweight, dependency-free probe endpoint. For Kubernetes, prefer Laravel-native health routes or a supported health package that can separate liveness and readiness semantics.
- What health checks does pragmarx/health provide?
- The package is described as providing configurable checks for the database, cache, storage, queues, and other application services. The exact check set depends on its configuration and the version you pin. Treat any checks it reports as application-level signals, not as a complete production monitoring or tracing solution.
- Can pragmarx/health send notifications when a health check fails?
- Yes, the package can notify you when checks fail, with notification hooks described as part of its feature set. However, notification-provider integrations from a 2019 package may rely on APIs or SDKs that have changed. Validate every required channel, credentials, routing, and alert-fatigue controls before relying on it in production.
- Is pragmarx/health maintained and safe for production?
- pragmarx/health appears effectively unmaintained, with its last release in 2019 and weak ecosystem validation. Adopting it shifts dependency maintenance, security patching, and Laravel/PHP compatibility work onto your team. It is high risk for new or modernized services and should be limited to a short-lived legacy stopgap with explicit ownership and a replacement date.
- What are alternatives to pragmarx/health for Laravel health checks?
- For current Laravel applications, consider spatie/laravel-health, Laravel-native health routes, or an external uptime and monitoring service depending on whether you need liveness/readiness, business-transaction checks, or alerting. These options are more likely to be maintained and compatible with supported Laravel and PHP versions. Compare them against your notification channels, authentication requirements, and observability needs.
- How should I secure the health route exposed by pragmarx/health?
- Treat the health endpoint as sensitive because it can reveal service names, dependency status, and diagnostic details. Put it behind authentication or network restrictions, apply rate limiting, and remove or redact detailed diagnostics in responses. Also review route middleware and ensure notification credentials are not exposed through configuration or error output.
- Can I use pragmarx/health in a legacy Laravel app as a temporary stopgap?
- It may be acceptable only in a pinned legacy Laravel/PHP stack where a small monolithic app needs basic database, cache, storage, or queue checks and alerting. Position it as a temporary adapter behind an internal HealthCheckService interface, pilot it with rollback and alert-fatigue controls, and document a decommission or replacement plan within 6 to 12 months. Do not make it a platform standard or use it in greenfield services.