Configuring the Loggers

Updating the logging configuration is the same thing for both the DM and the agent.

By default, Roboconf classes use the JDK logging (java.util.logging).
However, when deployed in Karaf, logging is configured through Log4J. The bridge is enabled through Pax Logging.

To update the logging configuration, simply edit the etc/org.ops4j.pax.logging.cfg file in the Karaf installation.
Here is the default logging configuration that was defined for Roboconf loggers. In Roboconf’s custom Karaf distributions, this snippet is located at the end of the default Karaf logging configuration.

# Roboconf appender
log4j.logger.net.roboconf=INFO, roboconf
log4j.appender.roboconf=org.apache.log4j.DailyRollingFileAppender
log4j.appender.roboconf.datePattern='.'yyyy-MM-dd
log4j.appender.roboconf.layout=org.apache.log4j.EnhancedPatternLayout
log4j.appender.roboconf.layout.ConversionPattern=%d{ISO8601} | %-5.5p | %-16.16c{1} | %m%n
log4j.appender.roboconf.file=${karaf.data}/log/roboconf.log
log4j.appender.roboconf.append=true

Logs are rotated on a daily basis. The default logging level for the Roboconf classes is INFO.
All these logs are written in a specific file: data/log/roboconf.log (under the Karaf directory).

Editing and saving this file will automatically propagate the new logging configuration.
You can also use Karaf commands to update the logging configuration. See Karaf’s web site for more information.

Be careful about log level names.

Roboconf bundles use the JDK logging. Level names include SEVERE, WARNING, INFO, FINE, FINER and FINEST. However, Log4J use other names. And there is not an exact matching between the levels. The Pax project gives the equivalence it took on its web site.

We reproduce this table here.

In the cfg file, you must use Log4J levels.
They will be converted into levels for the JDK logging.