|
Default Parameters for CtxNsIsWebCtTest
This test tracks requests from every client connecting to the web servers managed by a NetScaler appliance, and reports the requests count, bandwidth usage, page rendering time, and the network latency for each client. From these metrics, administrators can easily infer which client is imposing the maximum load on the web servers. Moreover, if help desk receives frequent complaints of slowness from users connecting from a particular client, then administrators can use the metrics reported by this test to isolate the source of the delay – is it because the client is unable to render the response pages quickly? is it because of a latent client network? or is it owing to a contention for bandwidth resources?
This page depicts the default parameters that need to be configured for the CtxNsIsWebCtTest.
The TEST PERIOD list box helps the user to decide how often this test needs to be executed. It is recommended that you set the TEST PERIOD to 5 minutes. This is because, the Nitro API using which the eG agent collects metrics from Web Insight, is capable of capturing only the performance data related to the last 5 minutes.
To connect to Web Insight and collect the metrics it captures, the eG agent needs to be configured with the credentials of a user with read-only permissions to Web Insight. Type the name of this user against INSIGHT USERNAME text box and the password of this user against INSIGHT PASSWORD text box. Then, confirm the password by retyping it in the CONFIRM PASSWORD text box.
By default, Web Insight is not SSL-enabled. This is why, the SSL flag is set to No by default. If it is SSL-enabled, then change this flag to Yes.
Not all clients interacting with a web server may be worth monitoring. Some clients may be seldom used and hence may not require monitoring; some other clients may rarely encounter any slowdowns, and hence can be ignored when monitoring. Administrators may want to exclude such clients from monitoring, so that the strain on the eG agent is reduced. From the SHOW BY drop-down, you can pick the criterion based on which a client’s ‘monitoring worth’ is to be evaluated. The options here are: Render time and Requests. If the Render time option is chosen from the SHOW BY list, then the test will monitor only those clients for which the Render_time measure of this test registers a value equal to or above the value specified against SHOW ABOVE LIMIT. If the Requests option is chosen from the SHOW BY list, then the test will monitor only those clients for which the Requests measure of this test registers a value equal to or above the value specified against SHOW ABOVE LIMIT. By default, the SHOW ABOVE LIMIT is set to 30; this implies that, by default, the test will monitor only those clients that fulfill one of the below-mentioned conditions:
The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.
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.
|