-
Notifications
You must be signed in to change notification settings - Fork 17
12 Configure Application Logging
hkuich edited this page Nov 22, 2021
·
1 revision
For control of GraMi logging, add the following to your log4j2.xml configuration:
<Configuration>
<Appenders>
<Console name="Console">
<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
</Console>
<File name="logFile" fileName="grami-log.log"> <!-- change log file path here -->
<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
</File>
<File name="dataLogFile" fileName="grami-data-warn.log"> <!-- change data issue log file path here -->
<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
</File>
<Async name="AsyncLog">
<AppenderRef ref="logFile"/>
</Async>
<Async name="AsyncData">
<AppenderRef ref="dataLogFile"/>
</Async>
</Appenders>
<Loggers>
<Logger name="com.bayer.dt.grami.data" level="WARN">
<AppenderRef ref="AsyncData"/>
</Logger>
<Logger name="com.bayer.dt.grami" level="INFO"> <!-- change level to DEBUG or TRACE for more information. Set to INFO for large imports -->
<AppenderRef ref="Console"/>
<AppenderRef ref="AsyncLog"/>
</Logger>
<Root level="OFF" />
</Loggers>
</Configuration>
For tracking the progress of your importing, the suggested logging level for TypeDBLoader is "INFO". For more detailed output, set the level to DEBUG or TRACE at your convenience.