Namespace HealthCheckerDetails

The interval between health checks, in milliseconds. The default value is 10000 (10 seconds).

Example: {@code 10000} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The backend server port against which to run the health check. If the port is not specified, then the network load balancer uses the port information from the {@code Backend} object. The port must be specified if the backend port is 0.

Example: {@code 8080} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The protocol the health check must use; either HTTP or HTTPS, or UDP or TCP.

Example: {@code HTTP}

Base64 encoded pattern to be sent as UDP or TCP health check probe.

A regular expression for parsing the response body from the backend server.

Example: {@code ^((?!false).|\\s)*$}

Base64 encoded pattern to be validated as UDP or TCP health check probe response.

The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. The default value is 3.

Example: {@code 3} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The status code a healthy backend server should return. If you configure the health check policy to use the HTTP protocol, then you can use common HTTP status codes such as "200".

Example: {@code 200} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. The default value is 3000 (3 seconds).

Example: {@code 3000} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The path against which to run the health check.

Example: {@code /healthcheck}