Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
(message has no fields)
Used in:
Whether this addition is the result of the first ever health check on a host, in which case the configured :ref:`healthy threshold <envoy_v3_api_field_config.core.v3.HealthCheck.healthy_threshold>` is bypassed and the host is immediately added.
Used in:
The type of failure that caused this ejection.
[#next-free-field: 13]
Host ejection.
Host addition.
A health check was successful. Note: a host will be considered healthy either if it is the first ever health check, or if the healthy threshold is reached. This kind of event indicate that a health check was successful, but does not indicates that the host is considered healthy. A host is considered healthy if HealthCheckAddHealthy kind of event is sent.
Host failure.
Healthy host became degraded.
A degraded host returned to being healthy.
Timestamp for event.
Host metadata
Host locality
Used in:
The type of failure that caused this event.
Whether this event is the result of the first ever health check on a host.
Used in:
,Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Typed metadata for :ref:`Proxy protocol filter <envoy_v3_api_msg_extensions.filters.listener.proxy_protocol.v3.ProxyProtocol>`, that represents a map of TLVs. Each entry in the map consists of a key which corresponds to a configured :ref:`rule key <envoy_v3_api_field_extensions.filters.listener.proxy_protocol.v3.ProxyProtocol.KeyValuePair.key>` and a value (TLV value in bytes). When runtime flag ``envoy.reloadable_features.use_typed_metadata_in_proxy_protocol_listener`` is enabled, :ref:`Proxy protocol filter <envoy_v3_api_msg_extensions.filters.listener.proxy_protocol.v3.ProxyProtocol>` will populate typed metadata and regular metadata. By default filter will populate typed and untyped metadata.