security session request-statistics show-by-request
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Show session request statistics by request name
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The security session request-statistics show-by-request
command shows historical statistics for management session activity, categorized by request (command or API name).
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>|local}]
- Node-
Selects the sessions that match this parameter value. This identifies the node that processed the session.
[-interface {cli|ontapi}]
- Interface-
Selects the sessions that match this parameter value. This identifies the interface (CLI or ONTAPI) that processed the session.
[-request <text>]
- Request Name-
Selects the sessions that match this parameter value. This identifies the command associated with these requests.
[-total <integer>]
- Total Requests-
Selects the sessions that match this parameter value. This identifies the total number of requests that have been made on a session. The following commands are not counted: top, up, cd, rows, history, exit.
[-blocked <integer>]
- Blocked Requests-
Selects the sessions that match this parameter value. This identifies the number of requests that were blocked due to configured limits.
[-failed <integer>]
- Failed Requests-
Selects the sessions that match this parameter value. This identifies the number of requests that failed for any reason (including if they were blocked by configured limits).
[-max-time <integer>]
- Maximum Time (ms)-
Selects the sessions that match this parameter value. This identifies the maximum amount of time (in milliseconds) that any request took.
[-last-time <integer>]
- Last Time (ms)-
Selects the sessions that match this parameter value. This identifies the amount of time (in milliseconds) that the last request took.
[-active <integer>]
- Number Active Now-
Selects the sessions that match this parameter value. This identifies the number of currently active requests.
[-max-active <integer>]
- Max Number Active-
Selects the sessions that match this parameter value. This identifies the maximum number of concurrently active requests.
[-last-active-seconds <integer>]
- Seconds Since Last Request Start-
Selects the sessions that match this parameter value. When requests are active, this indicates the time (in seconds) since the last request started.
[-idle-seconds <integer>]
- Idle Seconds-
Selects the sessions that match this parameter value. When no requests are active, this indicates the time (in seconds) since the last request ended.
[-total-seconds <integer>]
- Total Seconds-
Selects the sessions that match this parameter value. This identifies the total time (in seconds) that have been taken by all completed requests; it does not include session idle time.
[-average-time <integer>]
- Average Time (ms)-
Selects the sessions that match this parameter value. This identifies the mean time spent processing requests.
[-success-percent <percent>]
- Success Percent-
Selects the sessions that match this parameter value. This identifies the percentage of successful requests.
[-blocked-percent <percent>]
- Blocked Percent-
Selects the sessions that match this parameter value. This identifies the percentage of requests that were blocked due to configured limits.
[-failed-percent <percent>]
- Failed Percent-
Selects the sessions that match this parameter value. This identifies the percentage of requests that failed for any reason (including if they were blocked by configured limits).
[-max-active-limit <integer>]
- Max-Active Limit (privilege: advanced)-
Selects the sessions that match this parameter value. This identifies the configured limit that is used to throttle or reject requests.
Examples
The following example illustrates displaying historical statistics for all management session activity on a specific node, with a specific request query.
cluster1::> security session request-statistics show-by-request -node node1 -request network* Node: node1 Interface: cli Idle Total Request Name Total Now Max Pass Fail Seconds Seconds Avg (ms) ------------------------- -------- --- --- ---- ---- -------- -------- -------- network interface create 2 0 1 100% 0 2556 0 485 network interface modify 1 0 1 100% 0 2518 0 34 network interface show 8 0 1 100% 0 2152 12 1614 network route create 1 0 1 100% 0 2135 0 45 network route show 2 0 1 100% 0 2145 0 17 5 entries were displayed. cluster1::>