Event Monitoring log configuration
The Event Monitoring feature uses the Apache Decanter log-appender to write the events to a local file. The Decanter Log-Appender creates by default a single output file and provides not much configuration directly to control the output. Therefore the Log-Appender is combined with a Log4J configuration in Talend Runtime which allows to create a rolling file with the related Log4j configuration.
Default configuration is provided for rolling file setup for Log4J to allow 10 rolling files with 500MB size for each file which means up to 5 GB of event monitoring data can be buffered local to the Talend Runtime.
The file location will be set to ${karaf.data}/ eventmonitoring/em.log.%i folder with .1, .2, .3 at the end for each rolling file. See the file ${karaf.data}//etc/org.ops4j.pax.logging.cfg for more details.
# Event Monitoring logger
log4j2.logger.eventmonitoring.name = org.apache.karaf.decanter.appender.log.LogAppender
log4j2.logger.eventmonitoring.level = INFO
log4j2.logger.eventmonitoring.appenderRef.EventMonitoring.ref = EventMonitoringAppender
log4j2.logger.eventmonitoring.additivity = false
# Event Monitoring appender
log4j2.appender.eventmonitoring.type = RollingRandomAccessFile
log4j2.appender.eventmonitoring.name = EventMonitoringAppender
log4j2.appender.eventmonitoring.fileName = ${karaf.data}/eventmonitoring/em.log
log4j2.appender.eventmonitoring.filePattern = ${karaf.data}/eventmonitoring/em.log.%i
log4j2.appender.eventmonitoring.immediateFlush = true
log4j2.appender.eventmonitoring.append = true
log4j2.appender.eventmonitoring.layout.type = PatternLayout
log4j2.appender.eventmonitoring.layout.pattern = %m\n
log4j2.appender.eventmonitoring.policies.type = Policies
log4j2.appender.eventmonitoring.policies.size.type = SizeBasedTriggeringPolicy
log4j2.appender.eventmonitoring.policies.size.size = 500MB
log4j2.appender.eventmonitoring.strategy.type = DefaultRolloverStrategy
log4j2.appender.eventmonitoring.strategy.max = 10 Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!