Comment by John Moser on Reguel Wermelinger's answer

John Moser — Mon, 03 Feb 2020 06:30:14 -0500

but thumbs up for access_log !

Comment by John Moser on Reguel Wermelinger's answer

John Moser — Mon, 03 Feb 2020 05:30:36 -0500

Thanks ... but the issue with the performance logging : one record is written in 2 rows. Would be easier to process it further if the record would be on one line.

Answer by Reguel Wermelinger

Reguel Wermelinger — Mon, 03 Feb 2020 02:51:27 -0500

Hey John

Yes, you can enable access_logs from tomcat by enabling the AccesLogValve. There is a sample line in the context.xml which you can un-comment to do so.

Regarding the Performance Logging. If setting the engine to debug mode almost crashes your isntance, you may try to activate debug level only for the performance logs. Do so by adding a new log appender ( as described here: https://developer.axonivy.com/doc/latest/engine-guide/monitoring/logging.html#runtime-log ) . And set only this appender to level debug - but keep the main logger on level warning or error.

Such a solution could look as follows:

<!-- Defines a log file called performance.log -->
<appender name="PerfLog" class="org.apache.log4j.DailyRollingFileAppender"> 
    <param name="File" value="${user.dir}/logs/performance.log"/> 
    <param name="DatePattern" value="'.'yyyy-MM-dd"/> 
    <layout class="org.apache.log4j.IvyLog4jLayout"> 
        <param name="DateFormat" value="HH:mm:ss"/>
    </layout> 
</appender>

<category name="ch.ivyteam.ivy.webserver.internal.PerformanceLogValve" class="ch.ivyteam.log.Logger">
  <appender-ref ref="PerfLog"/> 
  <priority value="DEBUG"/>
</category>

Answers to: Performance Logging

Comment by John Moser on Reguel Wermelinger's answer

Comment by John Moser on Reguel Wermelinger's answer

Answer by Reguel Wermelinger