LAT Log4J Configuration

data pipelines are now the preferred method for loading data into the ocient system for details, see docid\ xq0tg7yph vn62uwufibu the lat uses {{log4j2}} for https //logging apache org/log4j/2 x/ users can configure their logging setup however they would like the lat packages come with example log4j2 xml files that can be used directly, or modified by the user this xml code in the log4j2 xml file shows an example configuration \<?xml version="1 0" encoding="utf 8"?> \<configuration status="warn" strict="true" monitorinterval="30" packages="biz paluch logging gelf log4j2"> \<appenders> \<rollingrandomaccessfile name="httplog" append="true" filename="logs/http log" filepattern="logs/http %d{yyyymmdd hh} %i log gz" immediateflush="true"> \<patternlayout pattern="%m%n" /> \<policies> \<sizebasedtriggeringpolicy size="100 mb" /> \</policies> \<defaultrolloverstrategy> \<delete basepath="logs"> \<iffilename glob="http log gz" /> \<ifaccumulatedfilesize exceeds="5 gb" /> \</delete> \</defaultrolloverstrategy> \</rollingrandomaccessfile> \<rollingrandomaccessfile name="latlog" append="true" filename="logs/lat log" filepattern="logs/lat %d{yyyymmdd hh} %i log gz" immediateflush="false"> \<patternlayout pattern="%d{iso8601} % 5p \[%t] %m%n" /> \<policies> \<sizebasedtriggeringpolicy size="100 mb" /> \</policies> \<defaultrolloverstrategy> \<delete basepath="logs"> \<iffilename glob="lat log gz" /> \<ifaccumulatedfilesize exceeds="20 gb" /> \</delete> \</defaultrolloverstrategy> \</rollingrandomaccessfile> \<rollingrandomaccessfile name="errorlog" append="true" filename="logs/error log" filepattern="logs/error %d{yyyymmdd hh} %i log gz" immediateflush="false"> \<patternlayout pattern="%m%n" /> \<policies> \<sizebasedtriggeringpolicy size="100 mb" /> \</policies> \<defaultrolloverstrategy fileindex="nomax"> \<delete basepath="logs"> \<iffilename glob="error log gz" /> \<ifaccumulatedfilesize exceeds="20 gb" /> \</delete> \</defaultrolloverstrategy> \</rollingrandomaccessfile> \<! \<gelf name="graylog" host="udp\ graylog dev" port="12201" version="1 1" extractstacktrace="true"> \<field name="process name" literal="lat" /> \<field name="log level" pattern="% 5p" /> \<field name="thread" pattern="%t" /> \</gelf> \ > \</appenders> \<loggers> \<logger name="org apache kafka" level="info" /> \<logger name="com ocient lat sink ocient binders binder" level="info" /> \<! httpchannel at debug so that jetty preserves the stacktrace when logging uncaught exceptions > \<logger name="org eclipse jetty server httpchannel" level="debug" /> \<logger name="org eclipse jetty server requestlog"> \<appenderref ref="httplog" /> \</logger> \<logger name="com ocient lat sink file fileerrorsink" level="info" additivity="false"> \<appenderref ref="errorlog" /> \<! \<appenderref ref="graylog" /> \ > \</logger> \<logger name="software amazon awssdk" level="info" /> \<logger name="io netty" level="info" /> \<root level="info"> \<appenderref ref="latlog" /> \<! \<appenderref ref="graylog" /> \ > \</root> \</loggers> \</configuration> relevant loggers org apache kafka {{kafka}} logger com ocient lat sink ocient binders binder lat binder logger can be verbose, recommended to keep at info level org eclipse jetty server httpchannel and org eclipse jetty server requestlog jetty logs for the http endpoint com ocient lat worker main worker logger containing important pipeline logs valid log levels are (in order of least to most verbose) error warn info debug trace log4j can be configured to log different packages at different levels as shown in the example here, the example logs the com ocient streaming client package at the trace level, but the remainder of the code is logged at info level related links docid\ tt6tfoulap0mt aycm2ka