Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

PDI logging

Parent article

You can troubleshoot issues without having to examine the comprehensive log of server executions with PDI logging. PDI logging contains transformation and job logs for both PDI client and Pentaho Server executions in a separate log file from the comprehensive logging data.

For information on comprehensive logging, see the Pentaho Logging article.

Set up the log file

Transformation and job logging is enabled by default, and the PDI client and Pentaho Server are configured separately. Perform the following steps to reconfigure the logging for the Pentaho Server or PDI client:


  1. Stop all relevant servers or exit the PDI client.

  2. Navigate to the following directory and open the log4j2.xml file with any text editor:

    Pentaho Serverserver/pentaho-server/tomcat/webapps/pentaho/WEB-INF/classes
    PDI clientdesign-tools/data-integration/classes
  3. Set your desired logging levels in the XML <Logger> elements for org.pentaho.di.trans.Trans and org.pentaho.di.job.Job. You can set different logging levels for transformations than for jobs. The following table maps PDI logging levels to the corresponding Apache Log4j levels:

    PDI Log LevelLog4j Log Level
  4. Set your desired log file rotation (rollingPolicy) value by editing the FileNamePattern parameter in the log4j2.xml file for the pdi-execution-appender. The parameters are:

    yyyy-MM-ddSpecify a daily rotation (Default).
    yyyy-MMSpecify a monthly rotation.
    yyyy-MM-dd-HH-mmSpecify a rotation every minute.
  5. Save and close the file, then start all affected servers or the PDI client to test the configuration.

Use the log file

The log files are located in the following directories:
Pentaho Serverserver/pentaho-server/logs/pdi.log
PDI clientdesign-tools/data-integration/logs/pdi.log
Navigate to a log file and open the file to view the contents. The log entry fields in the log files are:
DateTimeStampDate and time of the log
LogThresholdLogging level (INFO, ERROR, DEBUG, WARN, or TRACE)
ThreadIDUnique key for the job or transformation execution
FilepathAbsolute path of the transformation or job
MessageLog message
The following is an example of a log entry:

2018-03-07 11:40:36.290 INFO <Launch transformation UUID: 1246b616-a845-4cbc-9f4c-8a4a2cbfb4f1> [C:\build\pdi-ee-client-\data-integration\samples\jobs\run_all\Run all sample transformations.kjb file:///C:/build/pdi-ee-client- FILENAME Variable and execute.kjb] Starting entry

This entry contains these values for the following fields:
DateTimeStamp2018-03-07 11:40:36.290
ThreadID<Launch transformation UUID: 1246b616-a845-4cbc-9f4c-8a4a2cbfb4f1>
Filepath[C:\build\pdi-ee-client-\data-integration\samples\jobs\run_all\Run all sample transformations.kjb file:///C:/build/pdi-ee-client-8.1.0...run_all/DefineFILENAME Variable and execute.kjb]
MessageStarting entry