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.

Procedure

  1. If it is not yet started, start the Tridion Monitoring Agent Windows service.
    Monitoring detects all processes that are up and running and producing a heartbeat, and writes their names to a file.
  2. Access the location where the Monitoring Windows service is installed and check for a file called RegisteredServices.xml. Open this file for editing.
  3. Find the location of the Monitoring configuration file:
    • On the Content Manager server, navigate to the config\ subfolder of %TRIDION_HOME% (defaults to C:\Program Files (x86)\Tridion\).
    • 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.
  4. In this location, open cd_monitor_conf.xml for editing.
  5. In the HeartbeatMonitoring element, in the Services subelement, create one Service subelement for each item in the file RegisteredServices.xml that looks as follows:
    <Service ServiceType="NAME" TimeoutValue="10m" />

    where NAME is the name of an item in RegisteredServices.xml. You can set the timeout value to any value you want.

    This causes Monitoring to listen for any services you list, and report an error if they do not produce heartbeats within the timeout period you specify.

  6. Save and close cd_monitor_conf.xml, and restart the Windows service.