Pentaho logs

When run from the command line, Pentaho automatically prints logs to stdout, which by default gets printed to the console screen. This can be redirected when Pentaho is started to a file or even to /dev/null if you don't want to see anything.

Message values

Messages in Pentaho logs begin with a timestamp and value. The value may be one of the following:

• DEBUG
• INFO
• WARN
• ERROR

BI Server logs

JBoss (Pentaho 1.x)

Messages generated by the startup sequence in a default setup are stored in "$PENTAHO/jboss/server/default/log/boot.log".

Runtime messages are recorded in "$PENTAHO/jboss/server/default/log/server.log". This file stores the information for the current day. At the end of the day, the file is renamed to server.log.{date} (where {date} is the date in YYYY-MM-DD format) and the file is created afresh for the new day.

Tomcat (Pentaho 2 +)

Tomcat writes logs to "$PENTAHO/tomcat/logs/catalina.out". This includes logs for applications in the tomcat/webapps/ directory. Pentaho also keeps its own separate logs in "$PENTAHO/tomcat/bin/pentaho.log".

Action sequence logs

The execution of action sequences is logged to the server log.

By default, action sequences are set to an ERROR debug level. You can change this in Design Studio to DEBUG if you are troubleshooting a problem in the execution of an xaction.

JFreeReport (Pentaho Reporting) log

See here.

Mondrian log

Mondrian logging is handled by log4j, and is disabled by default. To enable, add the following to pentaho.war/WEB-INF/classes/log4j.xml:

<category name="mondrian.sql">
  <priority value="DEBUG"/>
</category>

<category name="mondrian.mdx">
  <priority value="DEBUG"/>
</category>

<category name="mondrian.rolap.agg">
  <priority value="DEBUG"/>
</category>

For even more detail, remove the explicit Threshold element from the appenders:

<param name="Threshold" value="WARN"/>

When a Threshold is defined in an Appender, it overrides the individual category thresholds.

Once you restart the BI server, Mondrian will be logged to the console and to the file tomcat/bin/pentaho.log.

Resources

• http://mondrian.pentaho.org/documentation/configuration.php#Logging

Security log

• Turning on security logging
• Enabling Verbose LDAP Logging

Administration Console

To increase the level of logging in the Administration Console, edit the file enterprise-console/resource/config/log4j.xml. Look for the line:

<priority value ="warn" />

Change it to:

<priority value ="DEBUG" />

Restart the console and you will see more output in the terminal (stdout). To send the logs to a file, use a redirection arrow:

$ ./start.sh > console.log

Data Integration

Data Integration supports adjustable verbosity of logging:

• Spoon (GUI)
• Pan (run transformations)
• Kitchen (run jobs)
• As we known, PDI transformations can be data sources for Pentaho reports in BI server. However, how to embed PDI kettle into BI server logs? Please have look PDI log in BI server

References

• Get the logging verbosity under control