Configuration for various types of health checking.
Interval between consecutive health checks.
Maximum time to wait for a health check response.
Number of consecutive unhealthy checks before considering a host
Number of consecutive healthy checks before considering a host healthy.
If specified, Envoy will start health checking after for a random time in
ms between 0 and initial_jitter. This only applies to the first health
If specified, during every interval Envoy will add interval_jitter to the
If specified, during every interval Envoy will add interval_ms *
interval_jitter_percent / 100 to the wait time. If interval_jitter_ms and
interval_jitter_percent are both set, both of them will be used to
increase the wait time.
Allows to configure panic threshold for Envoy cluster. If not specified,
the default is 50%. To disable panic mode, set to 0%.
If set to true, Envoy will not consider any hosts when the cluster is in
‘panic mode’. Instead, the cluster will fail all requests as if all hosts
are unhealthy. This can help avoid potentially overwhelming a failing
Specifies the path to the file where Envoy can log health check events.
If empty, no event log will be written.
If set to true, health check failure events will always be logged. If set
to false, only the initial health check failure event will be logged. The
default value is false.
The “no traffic interval” is a special health check interval that is used
when a cluster has never had traffic routed to it. This lower interval
allows cluster information to be kept up to date, without sending a
potentially large amount of active health checking traffic for no reason.
Once a cluster has been used for traffic routing, Envoy will shift back
to using the standard health check interval that is defined. Note that
this interval takes precedence over any other. The default value for “no
traffic interval” is 60 seconds.
Bytes which will be send during the health check to the target
receive (optional, repeated)
Bytes blocks expected as a response. When checking the response,
“fuzzy” matching is performed such that each block must be found, and
in the order specified, but not necessarily contiguous.
The HTTP path which will be requested during the health check
requestHeadersToAdd (optional, repeated)
The list of HTTP headers which should be added to each health check
expectedStatuses (optional, repeated)
List of HTTP response statuses which are considered healthy
Reuse health check connection between health checks. Default is true.