eG Monitoring
 

Measures reported by CtxNsPQTest

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 CtxNsPQTests 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.

Outputs of the test: One set of results for the Citrix ADC VPX/MPX appliance being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Hits Indicates the number of times during the last measurement period the Netscaler 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 Netscaler appliance failed to match 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.

First_request Indicates the number of Priority 1 requests the NetScaler appliance received during the last measurement period. Number

 

Second_request Indicates the number of Priority 2 requests the NetScaler appliance received during the last measurement period. Number

 

Third_request Indicates the number of Priority 3 requests the NetScaler appliance received during the last measurement period. Number