 | The features described on this page are available through the Hyperic HQ Enterprise Subscription |
Configuring Response Time
Response Time measurements can be collected for Apache, iPlanet (SunONE), IIS, Tomcat, WebSphere and Weblogic. Each product requires configuration to allow HQ to collect response time data.
Apache
In order to collect response time metrics for Apache, a module must be built and installed in the Apache installation. The module is called mod_rt and is provided in the HQ Agent directory in a subdirectory called product_connectors. Details on how to build and install the module can be found in the Apache product specific documentation.
Once the module is installed, navigate to the Resource Configuration section, of the Inventory page for the Apache virtual host you wish to collect response time data for. Make the appropriate changes to enable response time by turning it on and entering the correct path to the response time log.
End user response time is data that tells you how fast the content being served by Apache is actually appearing in the end user's browser. This type of response time is more complicated to configure and require small changes to the content being served. If you wish to configure end user response time, please contact Hyperic support for more information.
Servlet
Response time for servlets is relatively easy to configure. All of the servlet products supported by Hyperic HQ require an additional XML fragment in their configuration to allow HQ to collect metrics. This XML fragment has a section for enabling response time that is commented out by default. The following comments in the XML fragment include information about how to enable response time, and how it works.
<!--
Uncomment the following line to enable response time logging.
The directory you specify as the param can include properties
referenced from the System.properties of the vm.
The ResponseTime log file will by default store the last 1 hour's
worth of response time data. This file gets truncated as soon as
data is succesfully sent into the server. The file is named uniquely
for each webapp in the form: yourContextName_HQResponseTime.log
If this fragment is included in the global web.xml for the container,
all webapps in it will generate response time data, and have logs
following the format described above. You can enable it individually
on each webapp as well if you dont want every webapp to generate
response time data
-->
To enable response time for servlets, simply uncomment the following XML in the fragment, and replace "/path/to/log/directory" with the appropriate directory on your system where servlet response time logs should be stored.
<init-param> <param-name>responseTimeLogDir</param-name> <param-value>/path/to/log/directory</param-value> </init-param>
For details on how to configure your specific servlet product please see the section on Servlet Product Configuration.