The trace levels that are currently supported are shown in the following table.
Table 1. Supported trace levels| Level |
Description |
|---|
| 0 |
No trace |
| 1 |
Basic statistics trace |
| 2 |
Full trace |
| 3 |
Service trace |
The traces are described as follows:
- Basic statistics trace
- Collects and outputs summary statistics. It is most useful for analyzing the performance of the
application.
- Full trace
- Provides a fully verbose trail of activity that is sufficient to diagnose many functional problems.
- Service trace
- Produces a detailed trace in binary format and should be activated on request of IBM®.
The trace level is set in an entry in the VALUE table:
Table 2. Trace level entry in the VALUE table| Category |
Key |
Value |
|---|
| CORE |
PROFILING_LEVEL |
0 | 1 | 2 | 3 |
In addition to the trace levels, specific instrumentation classes can be enabled and disabled. This allows
the instrumentation to be as lightweight as possible if needed to track down any timing-related issues. The
instrumentation classes are shown in the following table.
Table 3. Instrumentation classes| Class |
Description |
|---|
| MAPPERS |
Monitor mappers |
| MAPDOCS |
Monitor EndMapper and OutMapper documents |
| EVENTS |
Monitor events |
| TRANSITIONS |
Monitor transitions |
| ACTIONS |
Monitor actions |
| PUBLISH |
Monitor publishing |
| SQL |
Monitor SQL |
| CUSTOM |
Monitor custom activities |
For an instrumentation class to be active, the following VALUE table entry must include the
<
class name>=Y exactly as documented in the following table. It must have no
additional spaces or case deviations.
Table 4. Instrumentation class entry in the VALUE table| Category |
Key |
Value |
|---|
| CORE |
PROFILING_FLAGS |
MAPPERS=Y MAPDOCS=Y EVENTS=Y TRANSITIONS=Y ACTIONS=Y PUBLISH=Y SQL=Y CUSTOM=Y |
The values that are used to configure the size and number of trace files that are generated are shown in
the following table. All of the values are found in the VALUE table, in the CORE category.
Table 5. Service trace configuration values| Key |
Description |
Values |
Default Value |
|---|
| PROFILING_MAX_SVC_TRACE_SIZE |
Defines how many megabytes of data are written in wrap around mode in the service trace
files. |
2 - 100 |
10 |
| PROFILING_MAX_TRACE_FILE_SIZE |
Defines the maximum size the trace file is allowed to reach. |
Size of file in bytes |
10485760 |
| PROFILING_MAX_TRACE_FILES |
Defines maximum number trace files allowed. |
>0 |
10 |
Note: In order for all of these settings to take effect, the integration node must be restarted.