Same as envoy’s default HTTP health checker, but with some additions:
allows a custom path and method on the health check request per endpoint.
The http path to use can be overridden using endpoint metadata. The endpoint-specific
path should be in the “io.solo.health_checkers.advanced_http” namespace, under a string
value named “path”. The same can be done for the method by setting a string value
named “method”.
allows for health check responses to leverage the response body rather than just
the http status code returned. The response body can be parsed as json and complex
assertions can be made on fields parsed from the json or plaintext response body.
The default health response if none of the response health checks were matches. If omitted, defaults to healthy. Note for devs: we’d probably prefer this default to unhealthy, but since the version of protoc we’re on doesn’t support optional scalars without an experimental flag, we cannot have the no_match_health field default to unhealthy while the match_health field defaults to healthy. As such, we offload this defaulting behavior to the control plane. For more reading, see https://github.com/protocolbuffers/protobuf/issues/1606#issuecomment-618687169.
Extract information from the request/response body. Only one of body or header can be set.
regex
string
Only strings matching this regular expression will be considered a match. The most simple value for this field is ‘.*', which matches the whole source. The field is required.
