Get desktop application:
View/edit binary Protocol Buffers messages
Describe an call (either incoming or outgoing). All requests (could be more than 1 for streaming RPC) and responses are given by this structure.
Used in:
Tags set by the framework.
Tags set by user, the framework treats it as opaque.
Logs written by user. These logs are not significant to the framework and can be safely dropped when duming the call.
Packets received / sent. For streaming RPCs there can be multiple packets (possibly in each side).
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:
How much time passed since start of this RPC (i.e., `Call`) when this packet is sent / received. In nanoseconds.
Context captured by binlog provider.
Context saved by the framework. This field is opaque to the implementation, and must be preserved as-is.