Logging configuration in JRDS

Jrds use log4j for logging. But this library can need quite a lot of thinking before a useful setup is done. So jrds wrap it for a faster setup and provide fast configuration elements.

The log setting properties are :

• nologging: disable totally the logs
• logfile: where the logs are to be written.
• loglevel: the default log level, taken from {trace, debug , info, warn, error, fatal}.
• log.{trace, debug , info, warn, error, fatal}: specify the log level for a comma separated list of class.
• log4jxmlfile: the path to a log4J XML file that will override the jrds log configuration.
• log4jpropfile: the path to a log4J properties file that will override the jrds log configuration.

By default, logs are send in the file indicated by the logfile property which is then rotated on a weekly basis.

The log.level properties are wrapping around log4j setup and set the logging level of the indicated classes. For ease of developpement there is some magic in probes and starters. As there is a lot of heritage in them, it might needs a lot of differents classes set to debug to follow a probe. So special loggers are build called jrds.Probe.ProbeName and jrds.Starter.StarterName that follows the operation of a probe and a starter between the differents level of heritage.

The log4xmlfile and log4jpropfile can be used by peoples fluent on log4j and wanting fine tune control on it.