Download the PHP package browncat/healthcheck-bundle without Composer

Health Check Bundle

This bundle can be used to easily write health checks and expose endpoints which can be used by e.g. Kubernetes to determine the health of the application.

This bundle consists of two core components that interweave with eachother, checkers and checks.

• A (health) check is an component which contains logic to check if the system is behaving correctly.
• A (health) checker runs these checks when needed. For example when the endpoint /healthz is requested.

Usage

This package can be installed using composer:

composer require browncat/healthcheck-bundle

Enable endpoints

This bundle comes with a set of endpoints which can be enabled to expose the following set of endpoints:

• /health/liveness Returns 503 if one or multiple checks fail. Coupled to LivenessChecker
• /health/readiness Returns 503 if one or multiple checks fail. Coupled to ReadinessChecker
• /health/startup Returns 503 if one or multiple checks fail. Coupled to StartupChecker
• /healthz JSON result of all checks, returns 503 if one or multiple checks fail.

To enable them all add the following to your routes.yaml:

Bundle provided health checks

This bundle comes with some pre defined health checks. These checks are not enabled by default as to not get into the way of your workflow. They can be enabled and configured through Symfony's config component.

Enable bundle provided health checks

To enable for example the check doctrine.connection create or modify the file config/packages/healthcheck.yaml and add the following:

A list of package provided health checks can be found here.

The config above will enable the doctrine connection check for all available checkers. To use a subset of checkers add the following to the config:

A list of availble checkers can be found here

List of bundle provided health checks

Creating your own health checks

Health checks are defined in classes extending Browncat\HealthCheckBundle\Check\HealthCheck. For example, you may want to check the connection between the application and a remote system:

Registering the health check

Health checks must be registered as services and tagged with the health_check.check tag. If you’re using the default services.yaml configuration, this is already done for you, thanks to autoconfiguration.

Naming a check

A check should have a common name. This makes sure it can be located if a big list of checks is executed. A check can be named by populating the proteced $name.

Passing or failing a check

A check can be failed or passed by passing a boolean value to the $succeeded propety.

Skipping a check

To skip a check set the property $skipped to true.

(Optional) set checkers

By default all checkers (readiness, liveness and maybe some other configured ones) run the check you've written. If you want to narrow the check down to only run with a specific checker populate public static $checkers with the class references of the desired checker.

List of available checkers

• Browncat\HealthCheckBundle\Checker\LivenessChecker
• Browncat\HealthCheckBundle\Checker\ReadinessChecker
• Browncat\HealthCheckBundle\Checker\StartupChecker
• Browncat\HealthCheckBundle\Checker\GlobalHealthChecker (this one processes all registered checks no matter what)