ONTAP 9.14.1 commands ( CA08871-226en )
snapmirror object-store profiler show
Availability: This command is available to cluster administrators at the advanced privilege level.
Description
The snapmirror object-store profiler show command is used to monitor progress and results of the snapmirror object-store profiler start command.
Parameters
- {
[-fields <fieldname>,…] -
If you specify the
-fields <fieldname>, …parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify. - |
[-instance ]} -
If you specify the
-instanceparameter, the command displays detailed information about all fields. [-node <nodename>]- Node Name-
This parameter specifies the node on which the profiler was started.
[-object-store-name <text>]- ONTAP Name for this Object Store Configuration-
This parameter specifies the object store configuration that describes the object store. The object store configuration has information about the object store server name, port, access credentials, and provider type.
[-object-name-prefix <UUID>]- Bin UUID-
This parameter specifies the object name prefix.
[-object-prefix <text>]- Prefix Added to Each Object-
If this parameter is specified, the command displays information only about the objects whose prefix matches the specified prefix.
[-profiler-status <text>]- Profiler Status-
Current status of the profiler.
[-start-time <MM/DD/YYYY HH:MM:SS>]- Profiler Start Time-
Time at which profiler run started.
[-op-name <text>]- Operation Name - PUT/GET-
Name of the operation. Possible values are PUT or GET.
[-op-size {<integer>[KB|MB|GB|TB|PB]}]- Size of Operation-
Size of the PUT or GET operation.
[-op-count <integer>]- Number of Operations Performed-
Number of operations issued to the object store.
[-op-failed <integer>]- Number of Operations Failed-
Number of operations that failed.
[-op-latency-minimum <integer>]- Minimum Latency for Operation in Milliseconds-
Minimum latency of the operation in milliseconds, as measured from the filesystem layer.
[-op-latency-maximum <integer>]- Maximum Latency for Operation in Milliseconds-
Maximum latency of the operation in milliseconds, as measured from the filesystem layer.
[-op-latency-average <integer>]- Average Latency for Operation in Milliseconds-
Average latency of the operation in milliseconds, as measured from the filesystem layer.
[-op-throughput {<integer>[KB|MB|GB|TB|PB]}]- Throughput per Second for the operation-
Throughput per second for the operation.
[-op-errors <text>,…]- Error Reasons and Count-
Error reasons and count for failed operation.
[-op-latency-histogram <text>,…]- Latency Histogram-
Latency histogram for the operation.
Examples
The following example displays the results of snapmirror object-store profiler start :
cluster1::>snapmirror object-store profiler show
