The storage aggregate object-store profiler show command is used to monitor progress and results of the storage aggregate 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 -instance parameter, the command displays detailed information about all fields.
[-node <nodename>] - Node Name: If this parameter is specified, the command only displays information corresponding to the specified node.
[-object-store-name <text>] - ONTAP Name for this Object Store Configuration: If this parameter is specified, the command only displays information about the objects which are placed on the specified object store.
[-object-name-prefix <UUID>] - Bin UUID: If this parameter is specified, the command displays information about all the objects whose object names are prefixed with the specified object name prefix. Objects from two different object stores will not have the same object name prefix.
[-object-prefix <text>] - Prefix Added to Each Object: If this parameter is specified, the command only displays information about the objects which have the specified prefix. Objects belonging to two different object stores can have the same object prefix.
[-profiler-status <text>] - Profiler Status: If this parameter is specified, the command only displays information corresponding to the specified node.
[-start-time <MM/DD/YYYY HH:MM:SS>] - Profiler Start Time: If this parameter is specified, the command only displays information corresponding to the specified start time of the profiler run.
[-op-name <text>] - Operation Name - PUT/GET: If this parameter is specified, the command only displays information corresponding to the specified operation name. Possible values are PUT or GET.
[-op-size {<integer>[KB|MB|GB|TB|PB]}] - Size of Operation: If this parameter is specified, the command only displays information corresponding to the specified size of the operation.
[-op-count <integer>] - Number of Operations Performed: If this parameter is specified, the command only displays information corresponding to the specified node.
[-op-failed <integer>] - Number of Operations Failed: If this parameter is specified, the command only displays information corresponding to the specified node.
[-op-latency-minimum <integer>] - Minimum Latency for Operation in Milliseconds: If this parameter is specified, the command only displays information corresponding to the specified minimum latency for the operation. The values are in milliseconds.
[-op-latency-maximum <integer>] - Maximum Latency for Operation in Milliseconds: If this parameter is specified, the command only displays information corresponding to the specified maximum latency for the operation. The values are in milliseconds.
[-op-latency-average <integer>] - Average Latency for Operation in Milliseconds: If this parameter is specified, the command only displays information corresponding to the specified average latency for the operation. The values are in milliseconds.
[-op-throughput {<integer>[KB|MB|GB|TB|PB]}] - Throughput per Second for the operation: If this parameter is specified, the command only displays information corresponding to the specified throughput for the operation.
[-op-errors <text>,…] - Error Reasons and Count: If this parameter is specified, the command only displays information corresponding to the count and specified reason for error.
[-op-latency-histogram <text>,…] - Latency Histogram: If this parameter is specified, the command only displays information corresponding to the specified latency histogram for the operation.

Examples

The following example displays the results of storage aggregate object-store profiler start :

cluster1::>storage aggregate object-store profiler show

storage aggregate object-store profiler start

ONTAP 9.13.1 commands

storage aggregate object-store profiler show

Description

Parameters

Examples

Related Links