ONTAP 9.14.1 commands

security session request-statistics show-by-vserver

Show session request statistics by Vserver

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The security session request-statistics show-by-vserver command shows historical statistics for management session activity, categorized by vserver.

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|rest}] - Interface

Selects the sessions that match this parameter value. This identifies the interface (CLI, ONTAPI, or REST) that processed the session.

[-vserver <vserver>] - Vserver

Selects the sessions that match this parameter value. This identifies the Vserver associated with this management session.

[-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 sessions.

[-max-active <integer>] - Max Number Active

Selects the sessions that match this parameter value. This identifies the maximum number of concurrently active sessions.

[-last-active-seconds <integer>] - Seconds Since Last Session Start

Selects the sessions that match this parameter value. When a session is active, this indicates the time (in seconds) since the last session started.

[-idle-seconds <integer>] - Idle Seconds

Selects the sessions that match this parameter value. When no sessions are active, this indicates the time (in seconds) since the last session 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

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 across the cluster, categorized by Vserver.

cluster1::> security session request-statistics show-by-vserver

Node: node1               Interface: cli                 Idle    Total
Vserver                      Total Now Max Pass Fail  Seconds  Seconds Avg (ms)
------------------------- -------- --- --- ---- ---- -------- -------- --------
cluster1                      2725   1   8  94%  146        -     3052     1120

Node: node1               Interface: ontapi              Idle    Total
Vserver                      Total Now Max Pass Fail  Seconds  Seconds Avg (ms)
------------------------- -------- --- --- ---- ---- -------- -------- --------
cluster1                         2   0   1 100%    0     2742        0       18

Node: node2               Interface: cli                 Idle    Total
Vserver                      Total Now Max Pass Fail  Seconds  Seconds Avg (ms)
------------------------- -------- --- --- ---- ---- -------- -------- --------
cluster1                      2552   1   6  95%  117        -      705      276
3 entries were displayed.

cluster1::>

The following example illustrates displaying historical statistics for management session activity on a specific node, for a specific Vserver.

cluster1::> security session request-statistics show-by-vserver -node node1 -vserver cluster1

Node: node1               Interface: cli                 Idle    Total
Vserver                      Total Now Max Pass Fail  Seconds  Seconds Avg (ms)
------------------------- -------- --- --- ---- ---- -------- -------- --------
cluster1                      2747   1   8  94%  147        -     3055     1112

Node: node1               Interface: ontapi              Idle    Total
Vserver                      Total Now Max Pass Fail  Seconds  Seconds Avg (ms)
------------------------- -------- --- --- ---- ---- -------- -------- --------
cluster1                         2   0   1 100%    0     2902        0       18
2 entries were displayed.

cluster1::>
Top of Page