Priority Queuing - Global Test
The Citrix ADC appliance supports prioritization of client requests with its priority queuing feature. This feature allows you to designate certain requests, such as those from important clients, as priority requests and sends them to the “front of the line,” so that the appliance responds to them first. This allows you to provide uninterrupted service to those clients through demand surges or DDoS attacks on your website.
Where the Priority Queing feature is enabled, administrators would want to be alerted if there are incoming requests that match a configured priority queuing policy. They will also like to know the count of requests that have been assigned different priorities. This is where the Priority Queuing - Global test helps!
This test monitors incoming requests and alerts administrators if any of these requests match a priority queuing policy. The number of requests that did not match any policy is also captured and reported. If any of these numbers are unexpected, then its an indication to administrators that the policy configurations need a relook. The test also reports the count of requests that have been assigned different priorities as per the configured policies, so that administrators can instantly figure out how many high priority requests are pending processing.
Target of the test : A Citrix ADC VPX/MPX
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the Citrix ADC VPX/MPX 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, NetScaler Password, and Confirm Password |
To monitor an 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. Then, confirm the password by retyping it in the Confirm Password text box. |
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 |
---|---|---|---|
Hits |
Indicates the number of times during the last measurement period the ADC appliance matched an incoming request using any priority queuing policy. |
Number |
If the value of either of these measures is unusually high, it could hint at issues in how the priority queuing policies are configured. You may want to revisit the policies to check if they have been wrongly configured. |
Threshold failed |
Indicates the number of times during the last measurement period the ADC appliance failed to match an incoming request using any priority queuing policy. |
Number |
|
Priority 1 requests |
Indicates the number of Priority 1 requests the ADC appliance received during the last measurement period. |
Number |
|
Priority 2 requests |
Indicates the number of Priority 2 requests the ADC appliance received during the last measurement period. |
Number |
|
Priority 3 requests |
Indicates the number of Priority 3 requests the ADC appliance received during the last measurement period. |
Number |
|