Smile CDR uses the Logback logging framework to emit system logs. System logs are generated at runtime by all components of the CDR, and they can be tweaked based on individual requirements.
Note that this section refers only to system logs, which are separate from the transaction logs (message/transaction payloads that have been received or sent) and the audit logs (activity performed by a given user).
By default, the system will produce the following log files:
||This file contains information emitted during startup and shutdown of the system||Logs are rotated and compressed when they reach 5 Mb in size, and 9 historical files are kept|
||This file contains general runtime information about what the system is doing, and can be useful in diagnosing runtime issues||Logs are rotated and compressed on a daily basis. By default logs are kept for 30 days, although this can be configured|
||This file contains any errors generated by the system (these error messages may also appear in other logs but are gathered here for convenience when troubleshooting)||Logs are rotated and compressed on a daily basis. By default logs are kept for 30 days, although this can be configured|
Logging configuration may be modified in the file
classes/logback.xml. This file contains some log definitions that must not be modified (and are labelled accordingly in the file) as well as other definitions that may be changed.
The logback debug context includes two properties:
moduleId is set to the running module, and the
requestId is set during request processing.
See the Logback Documentation for information on advanced settings that are possible.
moduleId debug property can be used with the logback MDCFilter or the GEventEvaluator filters to split logs files by module.
Note that the server polls
classes/logback.xml every 30 seconds by default, and will apply any changes; no restart is required. This too can be configured in
classes/logback.xml with the following configuration:
<configuration scan="true" scanPeriod="30 seconds">