Health checks for load balancing
Access Gateway load balanced protected resources can be managed automatically using health checks. Load balancing health checks:
- Are optional when configuring Access Gateway load balancing.
- Are disabled by default.
- Use HTTP Get operations to determine back end resource health.
- Can be configured in terms of expected HTTP return code, test interval, time-outs and more.
Protected web resources can be in one of three states:
| State |
Icon |
Description |
|---|---|---|
| Active |
|
Initial state, host entered and active but health unknown. When health checks are disabled, protected web resources never leave this state. |
| Healthy |
|
Host is responding based on health check settings. |
| Unhealthy |
|
Host isn't responding; new requests won't be routed to it. |
Health check fields
| Field | Value |
Default |
|---|---|---|
| Path | The URI path to the resource used in health check. | / |
| Method | The HTTP method used. | Always GET |
| Status code | The HTTP status code used to determine health. | 200 |
| Interval | The interval between health checks in seconds. | 10 |
| Request timeout | The health check request timeout in seconds. | 1 |
| Healthy threshold | The number of requests that must succeed before a host is considered healthy. | 3 |
| Unhealthy threshold | The number of requests that must fail before a host is considered unhealthy. | 3 |