Rudder

Historization logger is the only logger that is not integrated in an update, and was included in beta5 (#2321).

Every other loggers are present

In an update script, you have to add those 4 lines before the closing of configuration end tag in logback.xml :

   <logger name="historization" level="info" additivity="false">
     <appender-ref ref="OPSLOG" />
     <!-- comment the following appender if you don't want to have logs about report in both stdout and opslog -->
     <appender-ref ref="STDOUT" />
   </logger>

Nicolas PERRON wrote:

I'm not sure to know how to deal with this. sed seems to not be adapted to this work.

I have the feeling that the problem is the same than #2049 and the configuration should checked by CFEngine with a key value.

What your opinion, Jon ?

Well, it's certainly possible, albeit ugly:

if ! cat /opt/rudder/etc/logback.xml | perl -p0e 's/\n//g' | perl -p0e 's/<!--.(?:(?!-->).)*-->//g' | perl -p0e 's/> *</></g' | grep '<logger name="historization" level="info" additivity="false"><appender-ref ref="OPSLOG" /><appender-ref ref="STDOUT" /></logger>'
then
    sed -i 's%^ *</configuration>%   <logger name="historization" level="info" additivity="false">\n     <appender-ref ref="OPSLOG" />\n     <!-- comment the following appender if you dont want to have logs about report in both stdout and opslog -->\n     <appender-ref ref="STDOUT" />\n   </logger>\n </configuration>%' /opt/rudder/etc/logback.xml
fi

Jonathan CLARKE wrote:

Nicolas PERRON wrote:

I'm not sure to know how to deal with this. sed seems to not be adapted to this work.

I have the feeling that the problem is the same than #2049 and the configuration should checked by CFEngine with a key value.

What your opinion, Jon ?

Well, it's certainly possible, albeit ugly:

[...]

Ok, then I will use this command to insert the missing part of logback.xml

Applied in changeset commit:5ed0a1a4e137b61b7d1363d617e58642fe714301.

Applied in changeset commit:4cc2410b877bf142d24ba481a5bdabd1beb02c1e.