Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Request metrics
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.
Monitor and Tuning | Request Metrics
Prepare Servers for request metrics collection
Turns on the request metrics feature.
When unchecked, the request metrics function is disabled.
To enable request metrics, check the box, save the change, and restart the server. When it is checked, the server is ready to enable request metrics and you will not need to restart the server. Depending on what option is selected under...
Components to be instrumented
...request metrics instrumentation will be enabled/disabled in various components. Select All, None, or Custom. If you select Custom, specify which components you would like to enable.
Enable request metrics
Turn on the request metrics feature. When disabled, the request metrics function is disabled.
Components to be instrumented
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.
An edge transaction, defined as the first transaction that enters the application server without a parent correlator, will always be instrumented even if the corresponding component is disabled for instrumentation.
Trace level
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.
Include one of the following values:
None
No instrumentation.
Hops
Generates instrumentation information on process boundaries only. When this setting is selected, you see the data at the application server level, not the level of individual components such as enterprise beans or servlets.
Performance_debug
Generates the data at Hops level and the first level of the intra-process servlet and EJB call (for example, when an inbound servlet forwards to a servlet and an inbound EJB calls another EJB). Other intra-process calls like naming and service integration bus (SIB) are not enabled at this level.
Debug
Provides detailed instrumentation data, including response times for all intra-process calls. Requests to servlet filters will only be instrumented at this level.
Standard logs
Enable the request metrics logging feature.
Select this check box to trigger the generation of request metrics logs in the SystemOut.log file.
Since enabling the request metrics logging feature will increase processor usage, IBM recommends using this feature together with filters so that only selected requests are instrumented.
With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.
Application Response Measurement (ARM) agent
Enables request metrics to call an underlying Application Response Measurement (ARM) agent.
Before enabling ARM, install an ARM agent and configure it to the appropriate classpath and path, following the instructions of the ARM provider.
Specify ARM agent
Type of ARM agent to use.
The ARM 4.0 agent and Tivoli ARM 2.0 agent are supported.
ARM transaction factory implementation class name
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.
Filters
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.
Use HPEL to troubleshoot applications
Get performance data from request metrics
Monitor application flow