Application Flows Test
The Citrix ADC appliance is a central point of control for all application traffic in the data center. It collects flow and user-session level information valuable for application performance monitoring, analytics, and business intelligence applications. The AppFlow freature, when enabled on the ADC, transmits this information by using the Internet Protocol Flow Information eXport (IPFIX) format, which is an open Internet Engineering Task Force (IETF) standard defined in RFC 5101. Using UDP as the transport protocol, AppFlow transmits the collected data, called flow records, to one or more IPv4 collectors. The collectors aggregate the flow records and generate real-time or historical reports.
To enable administrators to promptly detect bottlenecks (if any) in the transmission of flow records to configured collectors, the Application Flows test runs periodic checks on data transmissions from the ADC appliance.
Target of the test : An ADC VPX/MPX
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the ADC appliance being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
The IP address of the host for which the test is being configured. |
NetScaler Username and NetScaler Password |
To monitor a ADC device, the eG agent should be configured with the credentials of a user with read-only privileges to the target ADC device. Specify the credentials of such a user in the NetScaler Username and NetScaler Password text boxes. |
SSL |
The eG agent collects performance metrics by invoking NITRO (ADC Interface Through Restful interfaces and Objects) APIs on the target ADC device. Typically, the NITRO APIs can be invoked through the HTTP or the HTTPS mode. By default, the eG agent invokes the NITRO APIs using the HTTPS mode. This is why, the SSL flag is set to Yes by default. If the target ADC device is not SSL-enabled, then the NITRO APIs can be accessed through the HTTP mode only. In this case, set the SSL flag to No. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Appflow transmitted |
Indicates the number of Appflow flows transmitted by the ADC during the last measurement period. |
Number |
|
Appflow not transmitted |
Indicates the number of Appflows that were not transmitted during the last measurement period. |
Number |
A high value is indicative of a transmission bottleneck. This could be owing to improper collector configuration or a bad network link between the appliance and the collector. |
Appflow data transmitted |
Indicates the amount of Appflow octets transmitted by the ADC during the last measurement period. |
MB |
|
Appflow data not transmitted |
Indicates the amount of Appflow octets that were not transmitted during the last measurement period. |
MB |
A high value is indicative of a transmission bottleneck. This could be owing to improper collector configuration or a bad network link between the appliance and the collector. |
Appflow data ignored |
Indicates the amount of Appflow octets that were ignored by the ADC during the last measurement period. |
MB |
|
Appflow packets ignored |
Indicates the number of Appflow packets that were ignored by the ADC during the last measurement period. |
Number |
|
Appflow packets not transmitted |
Indicates the number of Appflow packets that were not transmitted by the ADC during the last measurement period. |
Number |
A high value is indicative of a transmission bottleneck. This could be owing to improper collector configuration or a bad network link between the appliance and the collector. |
Appflow messages transmitted |
Indicates the number of Appflow messages transmitted by the ADC during the last measurement period. |
Number |
|