Default Parameters for CtxNsSureConnTest

This test monitors Sure Connect policiies and reports the count of requests that match one/more of these policies. The test also reveals how many times Sure Connect conditions are triggered, so that you can quickly detect if the conditions are being fired more frequently than you would like them to. Revisiting the policies and tweaking them (if required), can help streamline this process. Additionally, you can figure out when alternate content is served and when in-memory JavaScript is served by the Sure Connect feature. Error conditions such as corruption of Sure Connect cookies and requests from unsupported browsers are captured and promptly reported by this test.

This page depicts the default parameters that need to be configured for the CtxNsSureConnTest test.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the IP address of the host for which this test is to be configured.

• To monitor a NetScaler device, the eG agent should be configured with the credentials of a user with read-only privileges to the target NetScaler 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 (NetScaler Interface Through Restful interfaces and Objects) APIs on the target NetScaler 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 NetScaler 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.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.