Added by Gunter Rombauts, last edited by Thomas Morgner on Nov 01, 2009  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Get the logging verbosity under control 

Logging in Pentaho 1.6 is controlled at several locations, controlling the verbosity of specific components

Warning
This list is not complete Yet.




Jboss Logging (log4j)

This is the Jboss logging like it is in all jboss application, controlled by /server/default/conf/jboss-log4j.xml (The name of the xml file depends of the Jboss version)

This is typically what you see in the log: A date and then the logging level.

2008-01-15 15:48:10,154 INFO  \[STDOUT\] Pentaho BI Platform server is ready. (Pentaho BI Platform 1.6.2.GA.951 (class)) Base Url = http://bebrpentaho/pentaho/, Solution Path = /srv/jboss/pentaho/pentaho-solutions

If you want to turn on security logging it is explained in : Turning on Security Logging

Reference : Log4j manual

Pentaho Application Logging

This is controlled by a log4j file in /server/default/deploy/pentaho.war/WEB-INF/classes

You see the date and logging level like in the previous section. The difference is that there is a second date and second logging level. This second logging level is controlled by the log4j file under the pentaho.war subdirectory

2008-01-15 15:55:38,579 INFO  \[STDOUT\] 15:55:38,579 INFO  \[RuntimeContext\] eef169cb-c379-11dc-ba52-89b4a7e25426:RUNTIME:context-150232-1200408938171:session-region-list.xaction Output of "response" was present but output handler was null.

Reference : Log4j manual

xaction verbosity

Each xaction file contains a header section that controls the verbosity. 

<?xml version="1.0" encoding="UTF-8"?>
<action-sequence>
<title>%title</title>
<version>1</version>
<logging-level>DEBUG</logging-level>

The debug information is not written to a log file but it is shown in the browser, when the request fails. An output like the one below is what you can expect.

| Failed

---- |
| {color:red}Error: Kettle.ERROR_0006 - Unable to find the specified directory wms (org.pentaho.plugin.kettle.KettleComponent){color} Debug: Starting execute of cmc/IT/wms/GenerateReplenishmentList.xaction (org.pentaho.core.solution.SolutionEngine)\\
 Debug: Getting runtime context and data (org.pentaho.core.solution.SolutionEngine)\\
 Debug: Loading action sequence definition file (org.pentaho.core.solution.SolutionEngine)\\
 Debug: audit: instanceId=c0ab3cfd-c380-11dc-8cf7-252c7f23b63b, objectId=org.pentaho.core.runtime.RuntimeContext, messageType=action_sequence_start (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: validateComponent validating component KettleComponent (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: Validating component for action GenerateReplenishmentList.xaction (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Executing action sequence (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: Executing action definition: Iteration 0 (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: audit: instanceId=c0ab3cfd-c380-11dc-8cf7-252c7f23b63b, objectId=KettleComponent, messageType=component_execution_started (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: execute pre-audit (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: Setting component log level to DEBUG (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: Initializing component (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: executeComponent starting audited execute (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: execute validation=true (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Start of execute (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: creating meta-repository (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: populating meta-repository (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Finding repository metadata (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Getting repository instance (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Connecting to repository (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Finding directory (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Directory=wms (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Job=GenerateReplenishmentList (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Finding directory (org.pentaho.plugin.kettle.KettleComponent)\\
 Error: Kettle.ERROR_0006 - Unable to find the specified directory wms (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: Disconnecting (org.pentaho.plugin.kettle.KettleComponent)\\
 Debug: executeComponent finished audited execute (org.pentaho.core.runtime.RuntimeContext)\\
 Error: RuntimeContext.ERROR_0012 - ActionDefinition for KettleComponent did not execute successfully (org.pentaho.core.runtime.RuntimeContext)\\
 Debug: audit: instanceId=c0ab3cfd-c380-11dc-8cf7-252c7f23b63b, objectId=org.pentaho.core.runtime.RuntimeContext, messageType=action_sequence_failed (org.pentaho.core.runtime.RuntimeContext)\\
 Error: SolutionEngine.ERROR_0007 - Action sequence execution failed (org.pentaho.core.solution.SolutionEngine)\\ |
&nbsp;&nbsp;Server Version: Pentaho BI Platform 1.6.2.GA.951 (class)

 Mondrian Logging

Mondrian logging is controlled by the pentaho webapp's WEB-INF/classes/log4j.xml file.  Add the following lines to the log file:

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

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

The result appears in the console and pentaho.log.  One special note, you'll want to remove the explicit Threshold element from within the log4j.xml appenders.  When a Threshold is defined in an Appender, it overrides the individual category thresholds.

Kettle logging



 

JFree Reports - Classic Engine

The logging mechnism is explained here : JFree Reporting Logging Mechanism