Configuring the appender
The QSRollingFileAppender configuration is as follows:
<appender name="MyQSRollingFileAppender" type="Qlik.Sense.Logging.log4net.Appender.QSRollingFileAppender"> <param name="threshold" value="info" /> <param name="encoding" value="utf-8" /> <param name="file" value="C:/ProgramData/Qlik/Sense/Log/output.log"/> <param name="maximumfiletime" value="720" /> <param name="maximumfilesize" value="512KB" /> <layout type="log4net.Layout.PatternLayout"> <converter> <param name="name" value="rownum" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.CounterPatternConverter" /> </converter> <converter> <param name="name" value="longIso8601date" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.Iso8601TimeOffsetPatternConverter" /> </converter> <converter> <param name="name" value="hostname" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.HostNamePatternConverter" /> </converter> <converter> <param name="name" value="guid" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.GuidPatternConverter" /> </converter> <converter> <param name="name" value="user" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.ServiceUserNameCachedPatternConverter" /> </converter> <converter> <param name="name" value="encodedmessage" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.EncodedMessagePatternConverter" /> </converter> <converter> <param name="name" value="encodedexception" /> <param name="type" value="Qlik.Sense.Logging.log4net.Layout.Pattern.EncodedExceptionPatternConverter" /> </converter> <param name="ignoresexception" value="false" /> <param name="header" value="Sequence#	Timestamp	Level	Hostname	Logger	Thread	Id	User	 Message	Exception	Id2
" /> <param name="conversionpattern" value="%rownum{9999}	%longIso8601date	%level	%hostname	%logger	%thread	 %guid	%user	%encodedmessage	%encodedexception{innermostmessage}	%guid%newline" /> </layout> </appender>
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!