Log configuration files
Logging is configured via an XML-based log configuration file:
C:\Program Files (x86)\Eduserv\OpenAthens.Net\conf\oaLogSP.xml (typical)
These examples use the Apache version
A log configuration may specify multiple loggers. A logger specifies a level and an outputter type. Loggers must be uniquely named.
As is normal with log frameworks, log events emitted by the Atacama platform are classified at a particular level of severity. The available log levels, in ascending severity are:
There is an
AUDIT level, but this must be specified individually as it does not form part of the above hierarchy.
Level inclusion conditions
A logger will emit log events matching one or more levels. By default, specifying a level will include events at that level or levels that are more severe. For instance, a level of
FATAL events. It is also possible to specify a precise list of levels by specifying an exact inclusion condition via the inc parameter. For example, a list of the following two level elements is used to emit log events matching
INFO events only:
Each logger must have an outputter associated with it. As the name suggests, an outputter is used to output the messages to a particular destination such as the system console or a file.
The available outputters are:.
Outputs to a file on the local file system. This file may rollover on a
MONTHLY basis and is given a unique name based on the logger name, and date. The directory where the log files will be written must also be specified.
Pipes log messages to an external program. This could be used in conjunction with other programs such as Cronolog or .
File descriptor outputter
Sends logs to
Windows event logging
To do this you must firstly declare an additional XML namespace in the log configuration file. This namespace is used to specify Windows-specific extensions. Then use the eventLog outputter declared in this namespace. It is optionally possible to specify the name of a separate server if events are to be sent to a server other than the local host.