Monitoring SDL Web processes
This section explains how to set up and use Monitoring, a software component that allows you to monitor and report on the status of various SDL Web processes.
- Monitoring architecture
You can monitor various SDL Web processes by installing a Monitoring Agent on a machine that runs a process you want to monitor: either a machine that runs the Content Manager server, or a machine that runs one or more Content Delivery Server Roles. - Installing Monitoring
On the Content Manager server, you already installed Monitoring when you ran the Content Manager installer. On a machine that contains one or more Content Delivery Server Roles you intend to monitor, install the Monitoring Agent and possibly the Monitoring Agent Web service. - Processes a Monitoring Agent can monitor
A Monitoring Agent can monitor a number of Content Manager, Content Delivery, Translation Manager and Outbound E-mail 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. - Detecting heartbeat processes automatically
Monitoring can automatically detect processes that produce heartbeats, if they are up and running, and write them to a file. You can perform this detection to see the names of the processes and configure Monitoring to monitor them explicitly, so that you will also know if they are down. - Configuring processes to monitor
You configure the processes you want the Monitoring Agent to monitor in its configuration file, cd_monitor_conf.xml. - 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. - Monitoring configuration reference
cd_monitor_conf.xml specifies which Content Delivery processes to monitor. The configuration reference documentation describes the elements and attributes contained in the configuration file.