-
-
appqoepolicy
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
appqoepolicy
Statistics for AppQoS policy resource.
Properties
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
name |
|
Read-write | policyName.
Minimum length = 1 |
clearstats |
|
Read-write | Clear the statsistics / counters.
Possible values = basic, full |
qosavgserverttfb |
|
Read-only | Average Server Time-To-First-Byte in milliseconds calculated for this AppQoE policy. |
qosavgserverttfbrate |
|
Read-only | Rate (/s) counter for qosavgserverttfb |
qosavgserverttlb |
|
Read-only | Average Server Time-To-Last-Byte in milliseconds calculated for this AppQoE policy. |
qosavgserverttlbrate |
|
Read-only | Rate (/s) counter for qosavgserverttlb |
qosavgclientttlb |
|
Read-only | Average Client Time-To-Last-Byte in milliseconds calculated for this AppQoE policy. |
qosavgclientttlbrate |
|
Read-only | Rate (/s) counter for qosavgclientttlb |
totthroughput |
|
Read-only | Throughput in Kbps calculated on this AppQoE policy |
throughputrate |
|
Read-only | Rate (/s) counter for totthroughput |
totsvrlinkedto |
|
Read-only | Total number of server connections that were established through this AppQoE Policy |
svrlinkedtorate |
|
Read-only | Rate (/s) counter for totsvrlinkedto |
totcltrequests |
|
Read-only | Total number of client connections that were requested through this AppQoE Policy |
cltrequestsrate |
|
Read-only | Rate (/s) counter for totcltrequests |
totrequests |
|
Read-only | Total number of requests that were requested through this AppQoE policy |
requestsrate |
|
Read-only | Rate (/s) counter for totrequests |
totrequestbytes |
|
Read-only | Total number of requests bytes that were requested through this AppQoE policy |
requestbytesrate |
|
Read-only | Rate (/s) counter for totrequestbytes |
totresponse |
|
Read-only | Total number of responses received by this AppQoE policy |
responserate |
|
Read-only | Rate (/s) counter for totresponse |
totresponsebytes |
|
Read-only | Total number of response bytes received by this AppQoE policy |
responsebytesrate |
|
Read-only | Rate (/s) counter for totresponsebytes |
totjssent |
|
Read-only | Total number of in-memory responses sent instead of expected responses through this AppQoE policy |
jssentrate |
|
Read-only | Rate (/s) counter for totjssent |
totjsbytessent |
|
Read-only | Total bytes of in-memory responses sent through this AppQoE policy |
jsbytessentrate |
|
Read-only | Rate (/s) counter for totjsbytessent |
pipolicyhits |
|
Read-only | Number of hits on the policy |
pipolicyhitsrate |
|
Read-only | Rate (/s) counter for pipolicyhits |
Operations
(click to see Properties )
- GET (ALL)
- GET
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
get (all)
URL: http:// <netscaler-ip-address> /nitro/v1/stat/appqoepolicy Query-parameters: args http:// <netscaler-ip-address> /nitro/v1/stat/appqoepolicy? args=name: <String_value> ,detail: <Boolean_value> ,fullvalues: <Boolean_value> ,ntimes: <Double_value> ,logfile: <String_value> ,clearstats: <String_value>
Use this query-parameter to get appqoepolicy resources based on additional properties.
attrs http:// <netscaler-ip-address> /nitro/v1/stat/appqoepolicy? attrs=property-name1,property-name2
Use this query parameter to specify the resource details that you want to retrieve.
HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response: HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{ "appqoepolicy": [ {
"name":<String_value>,
"qosavgclientttlbrate":<Double_value>,
"totjssent":<Double_value>,
"responsebytesrate":<Double_value>,
"cltrequestsrate":<Double_value>,
"totthroughput":<Double_value>,
"requestbytesrate":<Double_value>,
"throughputrate":<Double_value>,
"totjsbytessent":<Double_value>,
"svrlinkedtorate":<Double_value>,
"totsvrlinkedto":<Double_value>,
"totresponse":<Double_value>,
"totresponsebytes":<Double_value>,
"qosavgserverttfb":<Double_value>,
"pipolicyhitsrate":<Double_value>,
"jssentrate":<Double_value>,
"qosavgserverttfbrate":<Double_value>,
"pipolicyhits":<Double_value>,
"qosavgclientttlb":<Double_value>,
"jsbytessentrate":<Double_value>,
"totcltrequests":<Double_value>,
"totrequests":<Double_value>,
"qosavgserverttlbrate":<Double_value>,
"responserate":<Double_value>,
"requestsrate":<Double_value>,
"totrequestbytes":<Double_value>,
"qosavgserverttlb":<Double_value>
}]}
<!--NeedCopy-->
get
URL: http:// <netscaler-ip-address> /nitro/v1/stat/appqoepolicy/ name_value><String> HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response: HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{ "appqoepolicy": [ {
"name":<String_value>,
"qosavgclientttlbrate":<Double_value>,
"totjssent":<Double_value>,
"responsebytesrate":<Double_value>,
"cltrequestsrate":<Double_value>,
"totthroughput":<Double_value>,
"requestbytesrate":<Double_value>,
"throughputrate":<Double_value>,
"totjsbytessent":<Double_value>,
"svrlinkedtorate":<Double_value>,
"totsvrlinkedto":<Double_value>,
"totresponse":<Double_value>,
"totresponsebytes":<Double_value>,
"qosavgserverttfb":<Double_value>,
"pipolicyhitsrate":<Double_value>,
"jssentrate":<Double_value>,
"qosavgserverttfbrate":<Double_value>,
"pipolicyhits":<Double_value>,
"qosavgclientttlb":<Double_value>,
"jsbytessentrate":<Double_value>,
"totcltrequests":<Double_value>,
"totrequests":<Double_value>,
"qosavgserverttlbrate":<Double_value>,
"responserate":<Double_value>,
"requestsrate":<Double_value>,
"totrequestbytes":<Double_value>,
"qosavgserverttlb":<Double_value>
}]}
<!--NeedCopy-->
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.