The logging API is divided into two sections - one dealing with meta data directives, and the second dealing with the logging system service interface. The logging metadata addresses the desription of a logging channel by a client. The description is encapsulated in the CategoriesDirective and CategoryDirective immutable directives.
Category directives describe the logging channel requirements, including channel name, priority, and a named logging target.
A logging manager is responsible for fulling the the requirements expressed by a caregory directive. This capability is defined by the LoggingManager interface. Implementations such as the LogKit factory plugin are established via the avalon repository system and can be parameterized using the LoggingCriteria interface.
The following table details the set of standard properties supported by Logging System.
| Property | Description |
|---|---|
| avalon.logging.configuration | URL referencing an external logging system configuration. |
| avalon.logging.bootstrap | A logging channel to be used during the bootstrapping phase. Classic logging priority values of DEBUG, INFO, WARN, ERROR may be assigned and will be resolved to a console logger with an equivalent priority. |
| avalon.logging.basedir | The base directory to use when constructing file based log targets. Defaults to the initial working directory declared by the repository initial context. |
| avalon.logging.debug | Debug flag used to override all logging channels to debug priority. The default falue is 'false'. |
| avalon.logging.update | If the value is larger than zero, the update is how many millisecond between re-configuring the logging system. Not all logging system will support this property, in which case it is completely ignored. The default value is 0. |
