package bosdyn.api.metrics_logging
Get desktop application:
View/edit binary Protocol Buffers messages
message
metrics_logging_robot.proto:18optional header = 1
Common request header.
message
metrics_logging_robot.proto:23optional header = 1
Common response header.
int32 first_sequence_number = 2
The inclusive sequence_number of the first entry in the store.
int32 last_sequence_number = 3
The inclusive sequence_number of the last entry in the store.
message
metrics_logging_robot.proto:34optional header = 1
Common request header.
repeated int32 sequence_numbers = 2
The robot will respond with the corresponding Snapshot for these sequence_numbers, if it has them.
message
metrics_logging_robot.proto:43optional header = 1
Common response header.
repeated snapshots = 2
Signed AbsoluteMetricsSnapshot messages corresponding to the request timestamps. The robot will exclude snapshots if: * They don't exist on the robot * If included, the snapshot would push the total response message size over the GRPC limit.
message
metrics_logging_robot.proto:55optional header = 1
Common request header.
repeated string keys = 2
If keys are specified, the GetMetricsResponse will only include parameters which match the keys. If no keys are specified, all parameters will be returned.
bool include_events = 3
Include events in the GetMetricsResponse. By default events will not be included.
message
metrics_logging_robot.proto:67optional header = 1
Common response header.
repeated parameters = 2
Current parameters for metrics.
repeated string missing_keys = 3
If any keys specified in the GetMetricsRequest are not present in the database, they'll be reported here.
repeated events = 4
Events included in the metrics.
message
absolute_metrics.proto:21* Stores a collection of AbsoluteMetrics. The scalar values stored in this structure are meant to be cumulative.
optional timestamp_start = 1
Assume two snapshots. One at time=t, and one at time=t-1. If we subtract the metrics of snapshot t-1 from the metrics of snapshot t, we'll get change in metrics. That change in metrics corresponds to the bounding time given by the following two timestamps. Note, when the user transitions from opt out to opt in, or the robot starts up for the first time, timestamp_start will be empty!
optional timestamp_end = 2
int32 sequence_number = 3
Monotonic number. Every time the robot creates a snapshot, this number will increment. It will be how the robot reports what snapshots are available, and how the client & proxy track what snapshots they have & still need.
string robot_serial_number = 4
string robot_species = 5
repeated parameters = 6
repeated events = 7
Robot events
message
signed_proto.proto:33* A custom signed format. Sequentially laid out: 4 bytes header 20 bytes fingerprint 512 bytes signature X bytes data. header -> When this format changes, we'll use the header to deliminate which format was used to generate this data. fingerprint -> The fingerprint of public key corresponding to the private key that was used to generate the signature. As keys rotate, this will allow the signature verifier to know what key to use to verify the signature. signature -> signature of the data field. data -> Contents specified by parent container. Usually contains a serialized protobuf.
Used in:
bytes data = 1