-
-
-
adc_application_summary
-
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!
adc_application_summary
Configuration for application summarized information resource.
Properties
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
issues_detected |
|
Read-write | Array of all app issues affecting health score. Each array element tells issueId, penalty and time when it occured.
Maximum length = 2048 |
ssl_rating |
|
Read-write | A+ / non-A+ / NA.
Maximum length = 50 |
appname |
|
Read-write | AppName.
Maximum length = 255 |
response_time |
|
Read-write | total time taken by the app to send response to client. |
vslbhealth |
|
Read-write | Vserver Health. |
appcategory |
|
Read-write | App Category.
Maximum length = 255 |
ip_address |
|
Read-write | Field to store the ip address as it is along with any extension.
Maximum length = 512 |
clnt_connections |
|
Read-write | Current Client Connections. |
vservertype |
|
Read-write | Vserver Tyoe.
Maximum length = 255 |
pkt_recvd_cur |
|
Read-write | Total Pkts Received. |
error_percentage |
|
Read-write | Number of 5xx response recieved wrt total requests. |
total_bytes |
|
Read-write | Session total bytes. |
srvr_connections |
|
Read-write | Current Server Connections. |
vservername |
|
Read-write | Vserver Name.
Maximum length = 255 |
pkt_sent_cur |
|
Read-write | Total Pkts Sent. |
curr_state |
|
Read-write | Current State.
Maximum length = 50 |
health_score |
|
Read-write | App Health Score. |
total_requests |
|
Read-write | Total Requests. |
throughput |
|
Read-write | Throughput .. |
application_class |
|
Read-only | Application class. |
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/adc_application_summary Query-parameters:
filter https://<MGMT-IP>/nitro/v2/config/adc_application_summary ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of adc_application_summary resources configured on the system. You can set a filter on any property of the resource.
pagesize=#no;pageno=#no https://<MGMT-IP>/nitro/v2/config/adc_application_summary ?pagesize=#no;pageno=#no Use this query-parameter to get the adc_application_summary resources in chunks.
count https://<MGMT-IP>/nitro/v2/config/adc_application_summary ?count=yes Use this query-parameter to get the count of adc_application_summary resources.
HTTPS Method: GET
Request Headers: Accept: application/json
X-NITRO-USER:username_value<String>
X-NITRO-PASS:password_value<String>
or
Cookie:NITRO_AUTH_TOKEN=token_value<String>
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, "adc_application_summary":[{
"issues_detected":<String_value>,
"ssl_rating":<String_value>,
"appname":<String_value>,
"response_time":<Double_value>,
"vslbhealth":<Integer_value>,
"appcategory":<String_value>,
"ip_address":<String_value>,
"clnt_connections":<Double_value>,
"vservertype":<String_value>,
"pkt_recvd_cur":<Double_value>,
"error_percentage":<Double_value>,
"total_bytes":<Double_value>,
"srvr_connections":<Double_value>,
"vservername":<String_value>,
"application_class":<String_value>,
"pkt_sent_cur":<Double_value>,
"curr_state":<String_value>,
"health_score":<Double_value>,
"total_requests":<Double_value>,
"throughput":<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.