Get desktop application:
View/edit binary Protocol Buffers messages
Log entry we store in binary logs
One of the above Type enum
One of the above Logger enum
Uniquely identifies a call. Each call may have several log entries, they will share the same call_id. 128 bits split into 2 64-bit parts.
The logger uses one of the following fields to record the payload, according to the type of the log entry.
Used by {SEND,RECV}_INITIAL_METADATA and {SEND,RECV}_TRAILING_METADATA. This contains only the metadata from the application.
Used by {SEND,RECV}_MESSAGE
Peer address information, will only be recorded in SEND_INITIAL_METADATA and RECV_INITIAL_METADATA entries.
true if payload does not represent the full message or metadata.
The method name. Logged for the first entry: RECV_INITIAL_METADATA for server side or SEND_INITIAL_METADATA for client side.
status_code and status_message: Only present for SEND_TRAILING_METADATA on server side or RECV_TRAILING_METADATA on client side.
An original status message before any transport specific encoding.
The value of the 'grpc-status-details-bin' metadata key. If present, this is always an encoded 'google.rpc.Status' message.
the RPC timeout
The entry sequence id for this call. The first GrpcLogEntry has a value of 1, to disambiguate from an unset value. The purpose of this field is to detect missing entries in environments where durability or ordering is not guaranteed.
Enumerates the entity that generates the log entry
Used in:
Enumerates the type of logs
Used in:
Message payload, used by REQUEST and RESPONSE
Used in:
This flag is currently used to indicate whether the payload is compressed, it may contain other semantics in the future. Value of 1 indicates that the binary octet sequence of Message is compressed using the mechanism declared by the Message-Encoding header. A value of 0 indicates that no encoding of Message bytes has occurred.
TODO(zpencer): this is changed because there is no uint8
Length of the message. It may not be the same as the length of the data field, as the logging payload can be truncated or omitted.
May be truncated or omitted.
A list of metadata pairs, used in the payload of CLIENT_INIT_METADATA, SERVER_INIT_METADATA and TRAILING_METADATA Implementations may omit some entries to honor the header limits of GRPC_BINARY_LOG_CONFIG. Implementations will not log the following entries, and this is not to be treated as a truncation: - entries handled by grpc that are not user visible, such as those that begin with 'grpc-' or keys like 'lb-token' - transport specific entries, including but not limited to: ':path', ':authority', 'content-encoding', 'user-agent', 'te', etc - entries added for call credentials
Used in:
A metadata key value pair
Used in:
Peer information
Used in:
will be removed: do not use
only for PEER_IPV4 and PEER_IPV6
Used in:
address is the address in 1.2.3.4 form
address the address in canonical form (RFC5952 section 4) The scope is NOT included in the peer string.
address is UDS string
Used to record call_id.
Used in: