Loading README.md +14 −0 Original line number Diff line number Diff line Loading @@ -1197,6 +1197,7 @@ The `GETLOG` operation gives the client access to log information. The request m * `CONFIGURATION` * `STATISTICS` * `MESSAGES` * `LIMITS` Below we will show the message structure used to request all types in a single `GETLOG` request. Loading Loading @@ -1248,6 +1249,7 @@ command { type: STATISTICS type: TEMPERATURES type: UTILIZATIONS type: LIMITS // Many utilization messages may be returned utilization { Loading Loading @@ -1345,6 +1347,18 @@ command { // bytes representing recent Kinetic Device log messages messages: "..." // limits that the device will enforce limits { maxKeySize = ... maxValueSize = ... maxVersionSize = ... maxTagSize = ... maxConnections = ... maxOutstandingReadRequests = ... maxOutstandingWriteRequests = ... maxMessageSize = ... } } } status { Loading kinetic.proto +13 −0 Original line number Diff line number Diff line Loading @@ -333,6 +333,7 @@ option java_outer_classname = "Kinetic"; CONFIGURATION = 3; STATISTICS = 4; MESSAGES = 5; LIMITS = 6; } repeated Utilization utilization = 2; Loading @@ -341,6 +342,7 @@ option java_outer_classname = "Kinetic"; optional Configuration configuration = 5; repeated Statistics statistics = 6; optional bytes messages = 7; optional Limits limits = 8; message Utilization { Loading Loading @@ -429,6 +431,17 @@ option java_outer_classname = "Kinetic"; optional uint64 bytes = 5; } message Limits { optional uint32 maxKeySize = 1; optional uint32 maxValueSize = 2; optional uint32 maxVersionSize = 3; optional uint32 maxTagSize = 4; optional uint32 maxConnections = 5; optional uint32 maxOutstandingReadRequests = 6; optional uint32 maxOutstandingWriteRequests = 7; optional uint32 maxMessageSize = 8; } } message Security { Loading Loading
README.md +14 −0 Original line number Diff line number Diff line Loading @@ -1197,6 +1197,7 @@ The `GETLOG` operation gives the client access to log information. The request m * `CONFIGURATION` * `STATISTICS` * `MESSAGES` * `LIMITS` Below we will show the message structure used to request all types in a single `GETLOG` request. Loading Loading @@ -1248,6 +1249,7 @@ command { type: STATISTICS type: TEMPERATURES type: UTILIZATIONS type: LIMITS // Many utilization messages may be returned utilization { Loading Loading @@ -1345,6 +1347,18 @@ command { // bytes representing recent Kinetic Device log messages messages: "..." // limits that the device will enforce limits { maxKeySize = ... maxValueSize = ... maxVersionSize = ... maxTagSize = ... maxConnections = ... maxOutstandingReadRequests = ... maxOutstandingWriteRequests = ... maxMessageSize = ... } } } status { Loading
kinetic.proto +13 −0 Original line number Diff line number Diff line Loading @@ -333,6 +333,7 @@ option java_outer_classname = "Kinetic"; CONFIGURATION = 3; STATISTICS = 4; MESSAGES = 5; LIMITS = 6; } repeated Utilization utilization = 2; Loading @@ -341,6 +342,7 @@ option java_outer_classname = "Kinetic"; optional Configuration configuration = 5; repeated Statistics statistics = 6; optional bytes messages = 7; optional Limits limits = 8; message Utilization { Loading Loading @@ -429,6 +431,17 @@ option java_outer_classname = "Kinetic"; optional uint64 bytes = 5; } message Limits { optional uint32 maxKeySize = 1; optional uint32 maxValueSize = 2; optional uint32 maxVersionSize = 3; optional uint32 maxTagSize = 4; optional uint32 maxConnections = 5; optional uint32 maxOutstandingReadRequests = 6; optional uint32 maxOutstandingWriteRequests = 7; optional uint32 maxMessageSize = 8; } } message Security { Loading