Get desktop application:
View/edit binary Protocol Buffers messages
Wrapper for tapped body data. This includes HTTP request/response body, transport socket received and transmitted data, etc.
Used in:
, , ,Body data as bytes. By default, tap body data will be present in this field, as the proto ``bytes`` type can contain any valid byte.
Body data as string. This field is only used when the :ref:`JSON_BODY_AS_STRING <envoy_v3_api_enum_value_config.tap.v3.OutputSink.Format.JSON_BODY_AS_STRING>` sink format type is selected. See the documentation for that option for why this is useful.
Specifies whether body data has been truncated to fit within the specified :ref:`max_buffered_rx_bytes <envoy_v3_api_field_config.tap.v3.OutputConfig.max_buffered_rx_bytes>` and :ref:`max_buffered_tx_bytes <envoy_v3_api_field_config.tap.v3.OutputConfig.max_buffered_tx_bytes>` settings.
Connection properties.
Used in:
, , ,Local address.
Remote address.
A fully buffered HTTP trace message.
Used in:
Request message.
Response message.
downstream connection
HTTP message wrapper.
Used in:
Message headers.
Message body.
Message trailers.
The timestamp after receiving the message headers.
A streamed HTTP trace segment. Multiple segments make up a full trace. [#next-free-field: 8]
Used in:
Trace ID unique to the originating Envoy only. Trace IDs can repeat and should not be used for long term stable uniqueness.
Request headers.
Request body chunk.
Request trailers.
Response headers.
Response body chunk.
Response trailers.
Sequence of read/write events that constitute a buffered trace on a socket. [#next-free-field: 6]
Used in:
Trace ID unique to the originating Envoy only. Trace IDs can repeat and should not be used for long term stable uniqueness. Matches connection IDs used in Envoy logs.
Connection properties.
Sequence of observed events.
Set to true if read events were truncated due to the :ref:`max_buffered_rx_bytes <envoy_v3_api_field_config.tap.v3.OutputConfig.max_buffered_rx_bytes>` setting.
Set to true if write events were truncated due to the :ref:`max_buffered_tx_bytes <envoy_v3_api_field_config.tap.v3.OutputConfig.max_buffered_tx_bytes>` setting.
Event in a socket trace. [#next-free-field: 6]
Used in:
,Timestamp for event.
Read or write with content as bytes string.
Connection information per event
The connection was closed.
TODO(mattklein123): Close event type.
Used in:
(message has no fields)
Data read by Envoy from the transport socket.
TODO(htuch): Half-close for reads.
Used in:
Binary data read.
Data written by Envoy to the transport socket.
Used in:
Binary data written.
Stream was half closed after this write.
A streamed socket trace segment. Multiple segments make up a full trace.
Used in:
Trace ID unique to the originating Envoy only. Trace IDs can repeat and should not be used for long term stable uniqueness. Matches connection IDs used in Envoy logs.
Connection properties.
Socket event.
Wrapper for all fully buffered and streamed tap traces that Envoy emits. This is required for sending traces over gRPC APIs or more easily persisting binary messages to files.
Used in:
An HTTP buffered tap trace.
An HTTP streamed tap trace segment.
A socket buffered tap trace.
A socket streamed tap trace segment.