The interval between health checks, in milliseconds.
Example: {@code 10000} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Specifies if health checks should always be done using plain text instead of depending on whether or not the associated backend set is using SSL.
If \"true\", health checks will be done using plain text even if the associated backend set is configured to use SSL.
If \"false\", health checks will be done using SSL encryption if the associated backend set is configured to use SSL. If the backend set is not so configured the health checks will be done using plain text.
Example: {@code false}
The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the {@code Backend} object.
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 TCP.
Example: {@code HTTP}
A regular expression for parsing the response body from the backend server.
Example: {@code ^((?!false).|\\s)*$}
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.
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.
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.
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}
The health check policy's configuration details.