CAG Sessions Test

This test monitors the sessions to the Citrix Access Gateway, exposes delays or other abnormalities in session creation/validation/loading, and stark inefficiencies (if any) in session cache utilization.

Target of the test : A Citrix Access Gateway

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Citrix Access Gateway being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which this test is to be configured.

Port

The port at which the specific host is listening.

Measurements made by the test

Measurement Description Measurement Unit Interpretation

CAG sessions started

Indicates the rate at which sessions were created on the Citrix Access Gateway.

Creates/Sec

 

CAG sessions updated

Indicates the rate at which the sessions were updated during the last measurement period.

Updates/Sec

 

CAG sessions validated

Indicates the rate at which sessions were validated during the last measurement period.

Validates/Sec

 

CAG sessions loaded

Indicates the rate at which sessions were loaded during the last measurement period.

Updates/Sec

 

CAG sessions saved

Indicates the rate at which sessions were saved during the last measurement period.

Saves/Sec

 

CAG sessions deleted

Indicates the rate at which sessions were deleted during the last measurement period.

Deletes/Sec

 

CAG session cache hits

Indicates the rate at which session requests were serviced by the session-cache during the last measurement period.

Hits/Sec

Ideally, this value should be high. A low value indicates that session requests are often fulfilled by direct disk accesses, thus increasing the processing overheads. You might want to increase the session cache size, if the situation persists. 

CAG session cache misses

Indicates the rate at which the session-cache could not service session requests during the last measurement period.

Misses/Sec

Ideally, this value should be low. A high value indicates that session requests are often fulfilled by direct disk accesses, thus increasing the processing overheads. You might want to increase the session cache size, if the situation persists.