The interval between health checks, in milliseconds.
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.
Example: {@code 8080} Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The protocol that the health check must use; either HTTP, 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.
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.
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 configuration details of the health checker.