Specify how much data to collect

This topic describes how to set the trace level to generate trace records in the administrative console.

Trace level specifies how much trace data to accumulate for a given transaction. We should choose the one of the following values when setting the trace level in the administrative console.

None

No instrumentation.

Hops

Generates instrumentation information on process boundaries only. When this setting is selected, we see the data at the application server level, not the level of individual components such as enterprise beans or servlets.

Generates instrumentation information on process boundaries only. When this setting is selected, we see the data at the application server level, not the level of individual components such as enterprise beans or servlets.

Performance_debug

Generates one additional level of instrumentation data, whereas debug generates detailed instrumentation data.

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 servlet and EJB calls.

Provides detailed instrumentation data, including response times for all intra-process calls.

Requests to servlet filters will only be instrumented at this level.

Tasks

1. Open the administrative console.

2. Click Monitor and Tuning > Request Metrics in the administrative console navigation tree.

3. Find Trace level in the Configuration tab.

4. Select a trace level from the drop down list box. To set the request metrics trace level to generate records, make sure that the trace level is set to a value greater than None.

5. Click Apply or OK.

6. Click Save.

Information are generated to reflect the trace level we selected.

What to do next

We must regenerate the web server plug-in configuration file as described in the Regenerating the web server plug-in configuration file topic after modifying the request metrics configuration.

Getting performance data from request metrics