Skip to content

Load Balancer Health Check

The load balancer checks each container port that receives traffic. A container that fails the check is taken out of service and replaced. By default the check requests / every 45 seconds.

Each check is a normal request to your application. For a CMS such as WordPress or Drupal, a request to / renders the home page: it runs PHP, loads plugins and reads files from shared storage. A check every 45 seconds, all day, can cost more than your real traffic. Point the check at a cheap path instead.

Images built on the Quant app-apache-php base image (including app-wordpress and app-drupal) answer /_quant/health with a static ok. Apache serves it directly: it does not run PHP or read your document root or volumes.

Use it when you want the check to confirm that the container answers, without the cost of a full page. If your application has its own health route (for example, one that checks the database), use that path instead.

Set it on the container that exposes the port.

Dashboard: open the container’s settings and fill in Load balancer health check: the path and the interval in seconds. Leave both empty to use the default.

Compose file: add service labels.

services:
wordpress:
image: ghcr.io/quantcdn-templates/app-wordpress:php8.3
ports:
- "80"
labels:
quant.healthcheck.path: /_quant/health
quant.healthcheck.interval: "60"

API: set loadBalancerHealthCheck on the container.

"loadBalancerHealthCheck": { "path": "/_quant/health", "intervalSeconds": 60 }
Setting Default Allowed values
Path (path) / Starts with /; up to 1024 characters
Interval (intervalSeconds) 45 15–300 seconds

An invalid value is rejected. Set loadBalancerHealthCheck to null, clear the dashboard fields, or remove the labels and import the compose file again to go back to the default. A saved change updates the load balancer straight away.

The check passes on any 2xx status and on 300, 301, 302, 304, 308, 400, 401, 403 and 404. Other statuses, such as 303, 307 or any 5xx, fail it. It shows that the container is up and answering requests. It does not show that every page of your application works. The startup grace period still controls how long a new container may fail the check while it boots.