package v1
Type Members
- final class Address extends GeneratedMessageV3 with AddressOrBuilder
Address information
Address information
Protobuf type
grpc.binarylog.v1.Address
- trait AddressOrBuilder extends com.google.protobuf.MessageOrBuilder
- final class BinaryLogProto extends AnyRef
- final class ClientHeader extends GeneratedMessageV3 with ClientHeaderOrBuilder
Protobuf type
grpc.binarylog.v1.ClientHeader
- trait ClientHeaderOrBuilder extends com.google.protobuf.MessageOrBuilder
- final class GrpcLogEntry extends GeneratedMessageV3 with GrpcLogEntryOrBuilder
Log entry we store in binary logs
Log entry we store in binary logs
Protobuf type
grpc.binarylog.v1.GrpcLogEntry
- trait GrpcLogEntryOrBuilder extends com.google.protobuf.MessageOrBuilder
- final class Message extends GeneratedMessageV3 with MessageOrBuilder
Message payload, used by CLIENT_MESSAGE and SERVER_MESSAGE
Message payload, used by CLIENT_MESSAGE and SERVER_MESSAGE
Protobuf type
grpc.binarylog.v1.Message
- trait MessageOrBuilder extends com.google.protobuf.MessageOrBuilder
- final class Metadata extends GeneratedMessageV3 with MetadataOrBuilder
A list of metadata pairs, used in the payload of client header, server header, and server trailer. Implementations may omit some entries to honor the header limits of GRPC_BINARY_LOG_CONFIG. Header keys added by gRPC are omitted. To be more specific, 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-' (with exception of grpc-trace-bin) 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 Implementations must always log grpc-trace-bin if it is present. Practically speaking it will only be visible on server side because grpc-trace-bin is managed by low level client side mechanisms inaccessible from the application level. On server side, the header is just a normal metadata key. The pair will not count towards the size limit.
A list of metadata pairs, used in the payload of client header, server header, and server trailer. Implementations may omit some entries to honor the header limits of GRPC_BINARY_LOG_CONFIG. Header keys added by gRPC are omitted. To be more specific, 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-' (with exception of grpc-trace-bin) 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 Implementations must always log grpc-trace-bin if it is present. Practically speaking it will only be visible on server side because grpc-trace-bin is managed by low level client side mechanisms inaccessible from the application level. On server side, the header is just a normal metadata key. The pair will not count towards the size limit.
Protobuf type
grpc.binarylog.v1.Metadata
- final class MetadataEntry extends GeneratedMessageV3 with MetadataEntryOrBuilder
A metadata key value pair
A metadata key value pair
Protobuf type
grpc.binarylog.v1.MetadataEntry
- trait MetadataEntryOrBuilder extends com.google.protobuf.MessageOrBuilder
- trait MetadataOrBuilder extends com.google.protobuf.MessageOrBuilder
- final class ServerHeader extends GeneratedMessageV3 with ServerHeaderOrBuilder
Protobuf type
grpc.binarylog.v1.ServerHeader
- trait ServerHeaderOrBuilder extends com.google.protobuf.MessageOrBuilder
- final class Trailer extends GeneratedMessageV3 with TrailerOrBuilder
Protobuf type
grpc.binarylog.v1.Trailer
- trait TrailerOrBuilder extends com.google.protobuf.MessageOrBuilder