Cache Policy Test

For many Citrix ADC features, policies control how a feature evaluates data. A policy uses a logical expression, called as rule, to evaluate data, and applies one or more actions based on evaluation. Alternatively, a policy can apply a profile, which defines a complex action.

This test auto-discovers policies and reports the count of connections that match every policy. This way, administrators can identify the policy that applies to the maximum number of connections.

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 each policy configured on the Citrix ADC VPX/MPX appliance being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the host for which the test is being configured.

NetScaler Username, NetScaler Password, and Confirm 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. Then, confirm the password by retyping it in the Confirm Password text box.


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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Policy hits

Indicates the count of requests that matched this policy during the last measurement period.


Compare the value of this measure across policy to know which policy label was applied to the maximum number of connections.

If this value is abnormally high for any policy, you may want to review the policy to verify if it has been correctly configured.

Policy undef hits

Indicates the count of requests for which this policy triggered an undefined event during the last measurement period.


An undefined event is triggered when the ADC cannot evaluate a policy, usually because it detects a logical or other error in the policy or an error condition on the ADC.

Ideally, the value of this measure should be 0.