Configuring processes to monitor

You configure the processes you want the Monitoring Agent to monitor in its configuration file, cd_monitor_conf.xml.

Procedure

  1. Find the location of the Monitoring configuration file:
    • On the Content Manager server, navigate to the config\ subfolder of %TRIDION_HOME%.
    • In a Content Delivery .NET web application, navigate to the bin\config\ subfolder of the web application root.
    • In a Content Delivery Java web application, navigate to the WEB-INF/classes/ subdirectory of the web application root.
    • When using a Content Delivery Windows service or Unix process, navigate to the config subdirectory of its installation folder.
  2. In this location, open cd_monitor_conf.xml for editing. You can configure two types of monitoring in this file:
    Heartbeat monitoring
    Monitoring of services that produce their own heartbeats for you to detect (push model). These services are listed in the HeartbeatMonitoring section. By default, Monitoring already detects these services if they are up and running and producing a heartbeat.
    Service Health monitoring
    Monitoring of services that require to poll its status (pull model). The polling of these services is configured in the ServiceHealthMonitorBindings section and ServiceHealthMonitors section.
  3. In the HeartbeatMonitoring element, activate monitoring of heartbeat services. If you have performed an automatic detection of processes that produce heartbeats, most of your processes will already be configured. The only processes you might want to add are services that you know by name, and that you know are down and therefore have not been detected.

    To activate monitoring of such services, inside the Services subelement, configure each of these services by inserting the following:

    <Service ServiceType="NAME" TimeoutValue="10m" />

    where NAME is the name of the undetected heartbeat service you intend to monitor. You can set the timeout to any value you want.

  4. For all pollable services that you intend to monitor, find out the type of Service Health Monitor needed to monitor it, that is, one of the following:
    • A WebDAV Service Health Monitor
    • An XML HTTPService Health Monitor
    • An HTTP Service Health Monitor
    • An RMI Service Health Monitor
    • A JMS Service Health Monitor
    • A JSON Post Service Health Monitor
  5. In the ServiceHealthMonitors element, add one Service Health Monitor element for each service you want to monitor. The name of the element must the Service Health Monitor type for that service, that is, the value of a Name attribute in one of the ServiceHealthMonitorBinding elements.
  6. Using the reference documentation in this documentation portal, learn about the subelements and attributes of the Service Health Monitor types you use, and configure them.
  7. Save and close the configuration file.