Default Parameters for CtxXcXACityTest

This test continuously monitors the resources taken up by a user's session on the server for each city. The results of this test can be used in troubleshooting and proactive monitoring. For example, when a user from a particular city reports a performance problem, administrators can quickly check the bandwidth utilized by that particular city's user, the CPU/memory/disk usage as well as the resource usage of user sessions established from other cities. The administrator also has access to details on the number of application processes launched by the users from each city and time taken for the same. This information can be used to spot a particular city from which the maximum number of application processes are launched on the target server.

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

• The TEST PERIOD list box, helps the user to decide how often this test needs to be executed. By default, this is 5 minutes.

• By default, the REPORT BY DOMAIN NAME flag is set to Yes. This implies that by default, this test will report metrics for every domainname\username configured for this test. This way, administrators will be able to quickly determine which user logged in from which domain. If you want the test to report metrics for the username alone, then set this flag to No.

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

• Once the necessary values have been provided, clicking on the UPDATE button will 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.