How to create an individual log file for Saiku Adhoc on Pentaho BI Server


saiku

Here I show an easy way of creatting an individual saiku.log file on your Pentaho BI server. An useful trick to organize and check saiku / saiku adhoc logs and debugging errors. I am sure you are familiar with mondrian_mdx and mondrian_sql  log files. These logs are disabled by default and may be enabled uncommenting  the blocks of code in the final part of the log file:

/biserver-ce/tomcat/webapps/pentaho/WEB-INF/classes/log4j.xml

…but why do I talk about these log files? The answer is easy, it’s because  we only need to create on this area another block of code containing the lines of code attached below and you will create a new saiku.log file!

Remember you can  change log  level from  DEBUG to ERROR,WARN…or the one most fits your requirements.


<appender name="SAIKULOG">

 <param name="File" value="../logs/saiku.log"/>
 <param name="Append" value="false"/>
 <param name="MaxFileSize" value="100MB"/>
 <param name="MaxBackupIndex" value="1"/>
 <layout>
 <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
 </layout>

 </appender>

<category name="org.saiku.adhoc">
 <priority value="DEBUG"/>
 <appender-ref ref="SAIKULOG"/>
 </category>

Restart your BI Server and from now on saiku log will appear into saiku.log individual file on /biserver-ce/tomcat/logs directory. However, don’t forget checking pentaho.log and catalina.out logs files to acquire all the information you require to solve your issues.

Have fun!