Healthchecks

Health checks verify that application components are running correctly and ready to receive traffic.

The platform periodically calls configured health endpoints. If a check fails, the corresponding replica is considered unhealthy and may be excluded from traffic until it recovers.

Health checks are also used during deployments to determine when a new version of the application is ready.

What this page helps you verify

The Healthchecks page allows you to verify that application components expose correct health endpoints and that the platform can monitor them.

From this page you can confirm:

• which applications expose health endpoints
• which endpoints are used for health verification
• whether monitoring for a specific application is enabled
• which healthchecks are managed by the platform and cannot be modified

Default health endpoints

Most applications provide default health endpoints used by the platform runtime.

Typical defaults include:

Some checks are platform-managed and cannot be disabled or modified to ensure correct runtime behavior.

Customizing healthchecks

For supported applications you can enable monitoring and customize the endpoint used for verification.

Typical workflow:

1. Ensure the application exposes a health endpoint (for example /health, /status, or /ready).
2. Open the Healthchecks page for the selected instance.
3. Enable the check or modify the endpoint if customization is supported.

Not all checks can be modified. Platform-managed healthchecks remain locked.

Role during deployments

Deployments use a Blue/Green strategy.

When a new version is deployed:

1. A new set of replicas is created.
2. Health checks verify that the new replicas are ready.
3. Traffic is switched to the new version.
4. Replicas from the previous version are terminated.

If health checks fail, traffic is not switched to the new version and the previous deployment continues serving traffic.