application commands
security session request-statistics show-by-location
Suggest changes
PDFs
Show session request statistics by location
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The security session request-statistics show-by-location command shows historical statistics for management session activity, categorized by client location.
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>|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.
[-location <text>]- Client Location-
Selects the sessions that match this parameter value. This identifies the location of the calling client application. This is typically the IP address of the calling client, or "console" or "localhost" for console or localhost connections.
[-ipspace <IPspace>]- IPspace of Location-
Selects the sessions that match this parameter value. This identifies the IPspace of the client location.
[-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 location.
cluster1::> security session request-statistics show-by-location Node: node1 Interface: cli Idle Total Location IPspace Total Now Max Pass Fail Seconds Seconds Avg (ms) ----------------- ------- -------- --- --- ---- ---- -------- -------- -------- console Default 21 1 1 100% 0 - 127 6063 localhost Default 2523 0 5 95% 115 20 280 111 Node: node1 Interface: ontapi Idle Total Location IPspace Total Now Max Pass Fail Seconds Seconds Avg (ms) ----------------- ------- -------- --- --- ---- ---- -------- -------- -------- 10.98.17.254 Default 2 0 1 100% 0 2419 0 18 Node: node2 Interface: cli Idle Total Location IPspace Total Now Max Pass Fail Seconds Seconds Avg (ms) ----------------- ------- -------- --- --- ---- ---- -------- -------- -------- console Default 6 0 1 83% 1 2941 423 70557 localhost Default 2502 0 5 95% 114 41 277 110 7 entries were displayed. cluster1::>
The following example illustrates displaying historical statistics for management session activity on a specific node and for a specific location.
cluster1::> security session request-statistics show-by-location -node node2 -location localhost Node: node2 Interface: cli Idle Total Location IPspace Total Now Max Pass Fail Seconds Seconds Avg (ms) ----------------- ------- -------- --- --- ---- ---- -------- -------- -------- localhost Default 2524 0 5 95% 115 30 279 110 cluster1::>