Get desktop application:
View/edit binary Protocol Buffers messages
Service for streaming access logs from Envoy to an access log server.
Envoy will connect and send StreamAccessLogsMessage messages forever. It does not expect any response to be sent as nothing would be done in the case of failure. The server should disconnect if it expects Envoy to reconnect. In the future we may decide to add a different API for "critical" access logs in which Envoy will buffer access logs for some period of time until it gets an ACK so it could then retry. This API is designed for high throughput with the expectation that it might be lossy.
Stream message for the StreamAccessLogs API. Envoy will open a stream to the server and stream access logs without ever expecting a response.
Identifier data that will only be sent in the first message on the stream. This is effectively structured metadata and is a performance optimization.
Batches of log entries of a single type. Generally speaking, a given stream should only ever include one type of log entry.
Empty response for the StreamAccessLogs API. Will never be sent. See below.
(message has no fields)
Wrapper for batches of HTTP access log entries.
Used in:
Used in:
The node sending the access log messages over the stream.
The friendly name of the log configured in :ref:`CommonGrpcAccessLogConfig <envoy_v3_api_msg_extensions.access_loggers.grpc.v3.CommonGrpcAccessLogConfig>`.
Wrapper for batches of TCP access log entries.
Used in: