Use this page to enable request metrics, select the components that are instrumented by request metrics, set trace levels, enable standard logs, enable Application Response Measurement (ARM), specify the type of ARM agent, and specify the ARM transaction factory implementation class name.
To view this administrative console page, click Monitoring and Tuning > Request Metrics.
Turns on the request metrics feature.
This turns on the request metrics feature. When disabled, the request metrics function is disabled.
Selects the components that are instrumented by request metrics.
When None is selected, no request metrics instrumentation will be enabled. When All is selected, request metrics instrumentation will be enabled in all the components listed under Custom. When Custom is selected, request metrics instrumentation will be enabled in the selected components.
Specifies how much trace data to accumulate for a given transaction. Note that Trace level and Components to be instrumented work together to control whether or not a request will be instrumented.
Enables the request metrics logging feature.
Enables request metrics to call an underlying Application Response Measurement (ARM) agent.
Before enabling ARM, you need to install an ARM agent and configure it to the appropriate classpath and path, following the instructions of the ARM provider.
Specifies the type of ARM agent that you want to use.
The ARM 4.0 agent and Tivoli® ARM 2.0 agent are supported.
Specifies the ARM transaction factory implementation class name in the package that is supplied by your provider. This field is required when ARM 4.0 agent is selected, but it is not required when Tivoli ARM agent is selected.
In this field, type the name of the ARM transaction factory implementation class that is present in the ARM library. Be sure to follow the instructions of the ARM provider and understand the name of the ARM transaction factory class for the installed ARM agent.
For more information, read the description of Transaction.ArmTransactionFactory.
When filtering is enabled, only requests matching the specified filter will generate request metrics data. Filters exist for source IP address, URI name, EJB method name, JMS parameters, and the WebServices parameters.