Monitoring SDL Tridion processes
This section explains how to set up and use Application Monitoring, a software component that allows you to monitor and report on the status of various SDL Tridion processes.
- Application Monitoring architecture
You can monitor various SDL Tridion processes by installing a Monitoring Agent on each machine that runs a process you want to monitor. - Processes a Monitoring Agent can monitor
A Monitoring Agent can monitor a number of Content Manager, Outbound E-mail, Online Marketing Explorer, and Content Delivery processes. You can monitor a process using a heartbeat monitor, which sends out a heartbeat on a configured interval, or a Service Health Monitor for which there are various types. - Installing a Monitoring Agent on a Content Manager server
A Monitoring Agent is installed and started automatically on the Content Manager Server when you run the SDL Tridion 2011 SP1 Content Manager installer. If you explicitly chose not to install the Monitoring Agent when you ran the installer, you need to rerun the installer. - Installing a Monitoring Agent on a Content Delivery server
You install a Monitoring Agent on a Content Delivery server using the Content Delivery installer or manually depending on your system setup. Additionally, you may need to add Web pages for monitoring and install the Web service - Setting up the Monitoring Agent Web service
If you intend for your monitoring management application to communicate with the Monitoring Agent through the Monitoring Agent Web service rather than by monitoring the log file or catching SNMP traps, you must set up the Monitoring Agent Web service as a Java Web application or as a .NET assembly. - Configuring processes to monitor
You configure the processes you want it to monitor in the Monitoring Agent cd_monitor_conf.xml configuration file. - Catching SNMP traps using an external application
For your external application to receive SNMP notifications (traps), you must configure its host name and port number in the configuration file of the Monitoring Agent and, depending on the SNMP version, select additional configuration options. - Interacting with the Application Monitoring Web service
You can access the Application Monitoring Web service through, for example, the SOAP protocol. The Web service exposes aTridionMonitoringAgentinterface with aGetStatus()method that returns an array ofServiceStatuselements. - Configuring the Monitoring Agent log file
Thelogback.xmlfile 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. - Configuring monitoring of endpoint with single sign-on (SSO) configured
To enable monitoring to monitor and endpoint with single sign-on, specify the endpoint and custom HTTP headers in your Monitoring configuration file. The headers you need to specify depend on the SSO product you use.