The logback.xml file is the configuration file for the logback logging framework used by Content Delivery. By default, the Monitoring Agent logs to a log file called cd_monitor.log located in the log/ subfolder of your Content Manager or Content Delivery installation.
Procedure
- Open the file
logback.xml in a plain-text editor or XML editor:
- On Content Manager, the file is located in the config\ subdirectory of
%TRIDION_HOME% (defaults to C:\Program Files (x86)\Tridion\).
- On Content Delivery, the file is located in the config/ (.NET) or /classes (Java) subfolder if Content Delivery is running as a Web application, otherwise in the config subdirectory of your Content Delivery installation.
- In the following
appender section, you can set properties for application monitoring:
<appender name="rollingMonitorLog" class="ch.qos.logback.core.rolling.RollingFileAppender">
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${log.folder}/cd_monitor.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>${log.history}</maxHistory>
</rollingPolicy>
<encoder><pattern>${log.pattern}</pattern></encoder>
<prudent>true</prudent>
</appender>
Note: For information on changing the logging level, the location to log to, the number of log files and the name of log files, see
Configuring logging on the Content Delivery server. Note that the logging level has no impact on application monitoring.
- Save and close
logback.xml.
Results
Monitoring Agent log files are generated for the configured processes. The log files contain lines of code in the following format:
[Info 11-12-2006 14:20:23] TMA-AG-99999 Status of service
'TransportService' changed to NotResponding
Where:
Info is an indication of the log level of the message (always set to Info )
- The timestamp indicates when the event was logged
TMA-AG-99999 is a unique code that identifies the Monitoring Agent and the message.
Status of service '<servicename>' changed to <status> is a message indicating which monitored process changed and how.