Agents Administration - Tests
 

Default Parameters for HttpStatusCodeTest

Using this test, eG Java BTM automatically categorizes business transactions to a target web site/application based on HTTP response status codes. The codes monitored by default are as follows:

  • 100 - 199 = Informational responses

  • 200 - 299 = Success responses

  • 300 - 399 = Redirection responses

  • 400 - 499 = Client errors

  • 500 - 599 = Server errors

For each HTTP response-based transaction group, the test then reports the count of transactions for which the corresponding response status was returned. In the process, the test alerts administrators to transactions that return HTTP error responses. The detailed diagnostics point administrators to the precise transaction requests for which the error responses were returned by the server. By rapidly pinpointing problem transactions and the HTTP error they encountered, the test saves time and labor involved in troubleshooting the errors.

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

  • The TEST PERIOD list box helps the user to choose how often should the test be executed.

  • As mentioned already, this test monitors the following status code patterns by default: 1xx, 2xx, 3xx, 4xx, and 5xx. This is why, the SPECIFIC STATUS CODE LIST is set to none by default. Sometimes however, application developers may custom-define new HTTP response codes to suit the needs of the application and its users. If the target application is associated with such codes, then you can configure this test to monitor these custom codes as well by providing a comma-separated list of these codes here - eg., 700,805,901

  • By default, for each status code, the detailed diagnosis of this test reports the top-10 transactions that returned a response of that code, starting with the oldest transaction. If the eG database in your environment is well-tuned and has space enough to store more number of transactions, then you may want detailed diagnostics to report more than 10 transactions. In this case, you can increase the value of MAX PER STATUS CODE DD LIST parameter. On the other hand, if you do not want to strain your eG database by adding more transaction records to it, then, you can choose to view less number of transactions as part of detailed diagnosis. For this, specify a number than less than 10 here.

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