Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
, , ,The name of the access log implementation to instantiate. The name must match a statically registered access log. Current built-in loggers include: #. "envoy.access_loggers.file" #. "envoy.access_loggers.http_grpc" #. "envoy.access_loggers.tcp_grpc"
Filter which is used to determine if the access log needs to be written.
Custom configuration that depends on the access log being instantiated. Built-in configurations include: #. "envoy.access_loggers.file": :ref:`FileAccessLog <envoy_api_msg_config.accesslog.v2.FileAccessLog>` #. "envoy.access_loggers.http_grpc": :ref:`HttpGrpcAccessLogConfig <envoy_api_msg_config.accesslog.v2.HttpGrpcAccessLogConfig>` #. "envoy.access_loggers.tcp_grpc": :ref:`TcpGrpcAccessLogConfig <envoy_api_msg_config.accesslog.v2.TcpGrpcAccessLogConfig>`
[#next-free-field: 12]
Used in:
, ,Status code filter.
Duration filter.
Not health check filter.
Traceable filter.
Runtime filter.
And filter.
Or filter.
Header filter.
Response flag filter.
gRPC status filter.
Extension filter.
Performs a logical “and” operation on the result of each filter in filters. Filters are evaluated sequentially and if one of them returns false, the filter returns false immediately.
Used in:
Filter on an integer comparison.
Used in:
,Comparison operator.
Value to compare against.
Used in:
=
>=
<=
Filters on total request duration in milliseconds.
Used in:
Comparison.
Extension filter is statically registered at runtime.
Used in:
The name of the filter implementation to instantiate. The name must match a statically registered filter.
Custom configuration that depends on the filter being instantiated.
Filters gRPC requests based on their response status. If a gRPC status is not provided, the filter will infer the status from the HTTP status code.
Used in:
Logs only responses that have any one of the gRPC statuses in this field.
If included and set to true, the filter will instead block all responses with a gRPC status or inferred gRPC status enumerated in statuses, and allow all other responses.
Used in:
Filters requests based on the presence or value of a request header.
Used in:
Only requests with a header which matches the specified HeaderMatcher will pass the filter check.
Filters for requests that are not health check requests. A health check request is marked by the health check filter.
Used in:
(message has no fields)
Performs a logical “or” operation on the result of each individual filter. Filters are evaluated sequentially and if one of them returns true, the filter returns true immediately.
Used in:
Filters requests that received responses with an Envoy response flag set. A list of the response flags can be found in the access log formatter :ref:`documentation<config_access_log_format_response_flags>`.
Used in:
Only responses with the any of the flags listed in this field will be logged. This field is optional. If it is not specified, then any response flag will pass the filter check.
Filters for random sampling of requests.
Used in:
Runtime key to get an optional overridden numerator for use in the *percent_sampled* field. If found in runtime, this value will replace the default numerator.
The default sampling percentage. If not specified, defaults to 0% with denominator of 100.
By default, sampling pivots on the header :ref:`x-request-id<config_http_conn_man_headers_x-request-id>` being present. If :ref:`x-request-id<config_http_conn_man_headers_x-request-id>` is present, the filter will consistently sample across multiple hosts based on the runtime key value and the value extracted from :ref:`x-request-id<config_http_conn_man_headers_x-request-id>`. If it is missing, or *use_independent_randomness* is set to true, the filter will randomly sample based on the runtime key value alone. *use_independent_randomness* can be used for logging kill switches within complex nested :ref:`AndFilter <envoy_api_msg_config.filter.accesslog.v2.AndFilter>` and :ref:`OrFilter <envoy_api_msg_config.filter.accesslog.v2.OrFilter>` blocks that are easier to reason about from a probability perspective (i.e., setting to true will cause the filter to behave like an independent random variable when composed within logical operator filters).
Filters on HTTP response/status code.
Used in:
Comparison.
Filters for requests that are traceable. See the tracing overview for more information on how a request becomes traceable.
Used in:
(message has no fields)