package flare.binlog.proto

Describe an call (either incoming or outgoing). All requests (could be more than 1 for streaming RPC) and responses are given by this structure.

string correlation_id = 1
map<string, string> system_tags = 2
Tags set by the framework.
map<string, string> user_tags = 10
Tags set by user, the framework treats it as opaque.
repeated string logs = 11
Logs written by user. These logs are not significant to the framework and can be safely dropped when duming the call.
repeated Packet incoming_pkts = 12
Packets received / sent. For streaming RPCs there can be multiple packets (possibly in each side).
repeated Packet outgoing_pkts = 13
bytes system_context = 14
If you're going to do a dry-run, the context must be preserved. This data is opaque to dumper implementation, you shouldn't try to parse it. Its format can change without further notice.

A single message sent / received during the RPC.

Used in: Call

uint64 time_since_start = 1
How much time passed since start of this RPC (i.e., `Call`) when this packet is sent / received. In nanoseconds.
bytes provider_context = 2
Context captured by binlog provider.
bytes system_context = 3
Context saved by the framework. This field is opaque to the implementation, and must be preserved as-is.

message Call