Rudder

I just remove the identifier length limit for logger.

Some admin could look to the new log and say:

• if the no-limit parameter is OK
• if not, what could be a good length ?

Note that Logbak has a tone of things that can be set in log lines, see: http://logback.qos.ch/manual/layouts.html#ClassicPatternLayout

It has been decided to add a specific kind of logger that will look like syslog output, and only logs operational events, with their own levels.

Example:

• when application start / stop,
• when a plugin is detected
• when a modification happens in the configuration
• when a (operation) problem occured

It is also accepted that logs in event logs don't need to appear in the syslog-kind of logs.

The first use case will be for report log.

So,

There is now a Scala ReportLogger, which must be used to report information to ops.

The logger behaviour is defined in logback.xml in the following XML directives:

  <property name="OPSLOG_DIR" value="/var/log/rudder/webapp-opslog" />

That property defined the directory into which the logs will be written.

  <appender name="OPSLOG" class="ch.qos.logback.core.FileAppender">
    <file>${OPSLOG_DIR}/rudder-webapp.log</file>
    <append>true</append>
    <encoder>
      <pattern>%d{MMM dd HH:mm:ss} ${HOSTNAME} rudder[%logger]: [%level] %msg%n</pattern>
    </encoder>
  </appender>

This is the new appender, with an almost syslog format.
The filename is "rudder-webapp.log", but perhaps an other name would be better ?
The date patter zero-pad days, a space-based padding is not available.

Last, the file are not rotated by logback, but could be if needed. The assumption was that log file rotation is more an system property than an application one.

Finally, we configure the logger for the first business case, reports:

   <logger name="report" 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>

As written, the current configuration output "report" log message in both OPSLOG and STDOUT appender (so that STDOUT get all logs, but it can changed).

Note that for each ops logger that we will want to do, we will have to also create a Scala ****Logger object with the corresponding name.

I pass the relay to NCH to implement actual log.

I think that bug should be closed: it's main goal, allowing to build log for the aim of operators using Rudder, is done.

Other ticket should be open to follow other queries, like #2799 (change log directory) and #2800 (rotate the log file).

This looks nice, thank you François and Nicolas!

It's OK for me !