Enabling Tracing

The IBM Application Gateway (IAG) provides configurable tracing capabilities that can aid in problem determination. Unlike message logs, trace logs (or tracing) are not enabled by default.
Trace data is intended primarily for use by IBM Software Support. Trace data might be requested as part of diagnosing a reported problem. However, experienced product administrators can use trace data to diagnose and correct problems in an IAG environment.

🚧

Note

Use trace with caution. It is intended as a tool to use under the direction of IBM Software Support. Messages from tracing are sometimes cryptic, are not translated, and can severely degrade system performance.

Trace logs are best suited to situations where a problem is easily reproduced, is short-lived in duration, and can be reproduced without significant trace generation from other system activity. Enabling tracing can adversely affect the performance of the IAG.

Configuration

In order to enable tracing the settings must be added to the IAG configuration YAML file in the logging tracing node. The configuration options are detailed in the YAML reference documentation: Tracing.

Example

An example configuration to enable tracing is provided below:

logging:
  tracing:
    - file_name: /var/iag/trace.log
      component: pdweb.debug
      level: 9
    - file_name: /var/iag/trace.log
      component: pdweb.http.transformation
      level: 5

Components