Operating Systems: i5/OS
Personalize the table of contents and search results
Specifying how much data to collect
This topic describes how to set the trace level to generate trace
records in the administrative console.
Overview
Trace level specifies how much trace data to accumulate for a given
transaction. You 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 (for example, a servlet request coming from a browser or a Web server
and a JDBC request going to a database).
- Performance_debug
-
Generates the data at Hops level and the first level
of the intra-process servlet and Enterprise JavaBeans (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.
Note: Requests to servlet filters will only
be instrumented at this level.
Procedure
- Open the administrative console.
- Click Monitoring and Tuning > Request metrics in
the administrative console navigation tree.
- Find Trace level in the Configuration tab.
- 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.
- Click Apply or OK.
- Click Save.
Results
Information are generated to reflect the trace level you selected.
What to do next
You 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.
}
Request metrics trace filters
Related tasks
Getting performance data from request metrics
|