-
-
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of Citrix ADC application configuration using StyleBooks
-
-
Use ADM log messages for managing and monitoring your infrastructure
-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
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!
View analytics for Web transactions
Web transaction analytics enables you to view detailed transactions for:
-
Response time > 500 ms
-
5xx errors
Note:
You can view only a few sample 2xx transactions for the selected application.
Prerequisites:
To view the web transaction analytics, you must:
-
Enable analytics.
-
Change the Web Transaction Settings to get the 2xx displayed. Navigate to Analytics > Settings, select Enable Features for Analytics, and select All.
Detailed web transactions
This feature not only enables you to look into the detailed transactions, but also understand the response time metric split across the client, ADC, and server visually.
You can access the Transaction Summary for:
-
Applications - Navigate to Applications > Dashboard, select an application, and Click Transaction Log.
-
Kubernetes apps - Navigate to Applications > Service Graph, and click a service and select Transaction Logs.
The Transaction Summary page is displayed for the selected application.
Hover the mouse pointer in App Response to view details such as RTT and processing time from Citrix ADC instance and the server.
The following example helps you analyze that the issue is from the server. The server response time indicates 10 seconds.
You can also drag and select to view the transactions for a specific duration.
View events
You can view the detailed information about a particular event. On the Transaction Summary panel, you can filter results by selecting the options from each metric.
For example, consider that you want to view 4xx transactions.
On the Transaction Summary panel, click Response code, and select 404 to view the result.
Click a transaction to view the details that display the metrics information from client to server.
For transactions that have SSL errors, the details are displayed for both client and server. The following SSL metrics are displayed:
-
SSL Protocol Version
-
SSL Front-end Failure
-
SSL Cipher Strength
-
SSL Key Strength
-
SSL Certificate Type
You can also click the SSL Frontend and SSL Backend metrics from the Transaction Summary panel to filter the results.
To filter the results, select the options available under Transaction Summary.
-
Browser: The browsers types used by the clients. For example: Chrome, Firefox.
-
Client OS: The client OS based on the User Agent details from the browser. For example: Windows
-
Device: The devices based on the User Agent details from the browser. For example: Tablet, Mobile.
-
Request Type: The transaction request type. For example: GET.
-
Response code: The response code received from the server. For example: 501, 404, 200.
-
Response content type: The transaction content type. If the client request is for text/html, then the response from the server must be text/html.
-
Frontend SSL Protocol Version: The SSL protocol version used by the clients. For example: SSLv3.
-
Frontend SSL Cipher Strength: The cipher strength based on the SSL certificate key size such as high, medium, and low.
-
Frontend SSL Key Strength: The SSL cipher strength is calculated from the SSL certificate key size. The key length defines the SSL algorithm security. For example: 2048
-
Frontend SSL Failure: The front-end SSL handshake error message. For example: SSL CLIENTAUTH FAILURE
-
Frontend SSL Certificate Type: The certificate type used by the client. For example: RSA, DSA, ECDSA, DH.
-
Backend SSL Protocol Version: The SSL protocols used by the server. For example: SSLv3
-
Backend SSL Cipher Strength: The cipher strength based on the SSL certificate key size such as high, medium, and low.
-
Backend SSL Key Strength: The SSL cipher strength is calculated from the SSL certificate key size. The key length defines the SSL algorithm security. For example: 2048
-
Backend SSL Certificate Type: The certificate type used by the server. For example: RSA, DSA, ECDSA, DH.
Add columns in the event list
You can click the button to choose the list of options and click Add Columns to get the details displayed.
Advanced search
The Transaction Summary also has a search text box and time duration list, where you can view the events as per your requirement. When you place the cursor in the search box, the search box gives you a list of search suggestions. You can also use operators in your search queries to narrow the focus of your search.
The following are the operators you can use for your search queries:
Operators | Description | Example | Output |
---|---|---|---|
= | Equals to some value | Transaction-ID = 129867048 | Displays the event for the transaction ID with 129867048 |
|
Greater than some value | App-Response-Time > 500 | Displays the events for the applications that have the app response with more than 500 ms |
< | Lesser than some value | App-Response-Time < 300 | Displays the events for the applications that have the app response time with less than 300 ms |
|
Greater or equal to some value | Total-Bytes >= 1024 | Displays the events for the transactions with greater or equal to 1 kb |
<= | Less or equal to some value | Total-Bytes <= 1024 | Displays the events for the transactions with lesser or equal to 1 kb |
!= | Not equal to some value | Response-code != 200 | Displays the events with all transactions, except the failed transactions. |
~ | Contains some value | Virtual-Server ~ mas | Displays the events for the virtual servers that have the name mas. |
For example, let us consider a scenario that you wanted to generate events for total bytes that are lesser than 300 bytes. You must specify the search queries as follows:
-
Specify the required word in the search box to get the related suggestions.
-
Select Total-Bytes and click again on the search text box, and select <.
-
Type the value 300.
-
Select the time period and click Search to view the events based on your search query.
The search result is displayed.
Save search
After you use the suggestions and operators, you can save the search query. You can then use it later from the list, instead of using the suggestions and operators again.
-
To save a search query, click the bookmark icon, specify a name of your choice, and then click Save.
-
To use the search query from the list, click the icon and select the search query from the list to display the results.
-
To remove the search query, click the icon, hover the mouse pointer on the saved search query, click Remove.
You can also click the bookmark icon and click Remove.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.