inactive_ica_session¶
Configuration for Af report for ICA Session InActive resource.
Properties¶
(click to see Operations )
| Name | Data Type | Permissions | Description |
|---|---|---|---|
| launch_duration | <Double> | Read-write | ica session launch duration.. |
| total_bytes | <Double> | Read-write | Total bytes accounted by this URL in sampled timeframe.. |
| pn_agent_version | <String> | Read-write | Name of ICA session pn agent version.
Minimum length = 1 Maximum length = 128 |
| client_latency | <Double> | Read-write | ica session client latency.. |
| application_enumeration_duration | <Double> | Read-write | Time taken for app enumeration to launch.. |
| serverside_rto | <Double> | Read-write | serverside rto.. |
| rpt_sample_time | <Double> | Read-write | Report Sample time.. |
| clientside_0_win | <Double> | Read-write | Client side 0 window count.. |
| bandwidth | <Double> | Read-write | Avg Bandwidth.. |
| session_setup_time | <Double> | Read-write | ICA Session setup time.. |
| clientside_rto | <Double> | Read-write | clientside rto.. |
| session_rtt | <Double> | Read-write | ICA Session rtt.. |
| __count | <Double> | Read-write | count.. |
| state | <String> | Read-write | ICA Session state.. |
| device_type | <String> | Read-write | Device Type.. |
| server_jitter | <Double> | Read-write | ICA User server jitter.. |
| id | <String> | Read-write | Id is ICA Session ID.
Minimum length = 1 Maximum length = 64 |
| client_jitter | <Double> | Read-write | ICA User client jitter.. |
| server_latency | <Double> | Read-write | ica session server latency.. |
| serverside_0_win | <Double> | Read-write | server side 0 window count.. |
| session_type | <Double> | Read-write | Session Type. |
| session_duration | <Double> | Read-write | session duration.. |
| ica_rtt | <Double> | Read-write | ICA rtt.. |
| client_srtt | <Double> | Read-write | client Smothen RTT.. |
| edt_type | <String> | Read-write | EDT Type.. |
| receiver_version | <String> | Read-write | Name of ICA session receiver version.
Minimum length = 1 Maximum length = 128 |
| vdi_image_name | <String> | Read-write | vdi_image_name. |
| up_time | <Double> | Read-write | ica session up time.. |
| client_tx_bytes | <Double> | Read-write | Client Side Tx bytes.. |
| client_rx_bytes | <Double> | Read-write | Client Side Rx bytes.. |
| server_srtt | <Double> | Read-write | server Smothen RTT.. |
| session_end_time | <Double> | Read-write | ICA Session end time.. |
Operations¶
(click to see Properties )
- GET (ALL)
Some options that you can use for each operations:
Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:
http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes
If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.
Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,
To do this, you must specify the username and password in the request header of the NITRO request as follows:
X-NITRO-USER: <username>
X-NITRO-PASS: <password>
Note: In such cases, make sure that the request header DOES not include the following:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Note: Mandatory parameters are marked in red and placeholder content is marked in green
The following parameters can be used in the nitro request : onerror <String_value>
Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.
Default value: EXIT
Possible values = EXIT, CONTINUE
get (all)¶
URL: https://<MGMT-IP>/nitro/v2/config/inactive_ica_session Query-parameters:
HTTPS Method: GET
Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error
Response Headers:
Content-Type:application/json
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "inactive_ica_session":[{
"hdx_desktop_username":<String_value>,
"launch_duration":<Double_value>,
"total_bytes":<Double_value>,
"client_ip_address":<String_value>,
"pn_agent_version":<String_value>,
"client_latency":<Double_value>,
"application_enumeration_duration":<Double_value>,
"serverside_rto":<Double_value>,
"server_ip_address":<String_value>,
"rpt_sample_time":<Double_value>,
"clientside_0_win":<Double_value>,
"bandwidth":<Double_value>,
"session_setup_time":<Double_value>,
"clientside_rto":<Double_value>,
"ica_app_name":<String_value>,
"session_rtt":<Double_value>,
"ica_user_name":<String_value>,
"__count":<Double_value>,
"state":<String_value>,
"device_type":<String_value>,
"server_jitter":<Double_value>,
"id":<String_value>,
"client_jitter":<Double_value>,
"server_latency":<Double_value>,
"serverside_0_win":<Double_value>,
"session_type":<Double_value>,
"session_duration":<Double_value>,
"ica_rtt":<Double_value>,
"client_srtt":<Double_value>,
"edt_type":<String_value>,
"ica_device_ip_address":<String_value>,
"receiver_version":<String_value>,
"vdi_image_name":<String_value>,
"up_time":<Double_value>,
"client_tx_bytes":<Double_value>,
"client_rx_bytes":<Double_value>,
"server_srtt":<Double_value>,
"session_end_time":<Double_value>}]}