object_store_client_op
CM table for exporting object store operation statistics. Object store operations are HTTP operations sent over TCP to manage objects on any object store.
Classic Object: object_store_client_op
Table Row IDs
ID Format | Aggregation Type | Comment |
---|---|---|
{instance_name} |
(not applicable) |
This represents the construction of the row ID field, which is a single unique string that identifies a row. |
Properties
This section describes the mapping between classic (ONTAPI) string counter names and REST property names.
Classic String Counter | REST Property | Description |
---|---|---|
node_name |
node.name |
System node name |
Counters
This section describes the mapping between classic (ONTAPI) numeric counter names and REST counter names.
Classic Numeric Counter | REST Counter | Description |
---|---|---|
stats |
stats |
Counter that indicates the number of object store operations sent, and their |
ops |
ops |
Counter that indicates the number of object store operations in total for |
average_latency |
average_latency |
Average latencies executed during various phases of command execution. The |
throughput_bytes |
throughput_bytes |
Counter that indicates the throughput for the corresponding object store command |
throughput_ops |
throughput_ops |
Counter that indicates the throughput for commands in operations per second. |
Property/Counter Content Changes
This section describes any output value differences between the classic (ONTAPI) string counter and the respective REST property. It also describes array label name changes between classic array counters and respective REST array counters.
REST Counter | Description |
---|---|
ops |
The counter labels have changed. All of the dashes '-' in the labels were changed to underscores '_'. |
average_latency |
The counter labels have changed. All of the dashes '-' in the labels were changed to underscores '_'. |
Table Aliases
This section describes aliases for aggregated tables.