security session request-statistics show-by-user
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Show session request statistics by username
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The security session request-statistics show-by-user
command shows historical statistics for management session activity, categorized by username. Entries for username 'autosupport' reflect commands that are executed by the AutoSupport OnDemand feature.
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.
[-username <text>]
- Username-
Selects the sessions that match this parameter value. This identifies the authenticated user 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 (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 across the cluster, categorized by username.
cluster1::> security session request-statistics show-by-user Node: node1 Interface: cli Idle Total Vserver Username Total Now Max Pass Fail Seconds Seconds Avg (ms) -------------- ---------- -------- --- --- ---- ---- -------- -------- -------- cluster1 admin 81 1 3 80% 16 - 1228 15171 diag 1 0 1 100% 0 1982 1511 1511958 autosupport 4 0 1 100% 0 - 0 17 Node: node1 Interface: ontapi Idle Total Vserver Username Total Now Max Pass Fail Seconds Seconds Avg (ms) -------------- ---------- -------- --- --- ---- ---- -------- -------- -------- cluster1 admin 2 0 1 100% 0 2585 0 18 Node: node2 Interface: cli Idle Total Vserver Username Total Now Max Pass Fail Seconds Seconds Avg (ms) -------------- ---------- -------- --- --- ---- ---- -------- -------- -------- cluster1 admin 6 1 1 83% 1 3106 423 70557 4 entries were displayed. cluster1::>
The following example illustrates displaying historical statistics for management session activity on a specific node and for a specific username.
cluster1::> security session request-statistics show-by-user -node node1 -username diag Node: node1 Interface: cli Idle Total Vserver Username Total Now Max Pass Fail Seconds Seconds Avg (ms) -------------- ---------- -------- --- --- ---- ---- -------- -------- -------- cluster1 diag 1 0 1 100% 0 - 1511 1511958 cluster1::>