How to Monitor the Health of InTrust Event Forwarding (4282184)

This article describes how you can set up improvised health monitoring for event forwarding from InTrust repositories in the absence of an integrated solution.

At this time, built-in self-auditing features in InTrust do not cover event forwarding activity. You can take advantage of the real-time monitoring capabilities as a workaround.

To install the configuration objects

1. Download the ForwardingStatusMonitoring.exe self-extracting archive from the Attachments section in this article.

2. Run the downloaded file to unpack its contents to a folder of your choice on any InTrust server in your InTrust organization.

3. Use the command prompt to import the unpacked data source, as follows:
   \Server\ADC\SupportTools\InTrustPDOImport.exe -import "\Repository Status Monitoring data source.xml"
   The resulting data source will become available in InTrust Manager in the Configuration | Data Sources node.

4. Use the command prompt to import the unpacked real-time monitoring rule, as follows:
   \Server\ADC\SupportTools\InTrustPDOImport.exe -import "\Repository Status Monitoring rule.xml"
   The resulting rule will become available in InTrust Manager in the Real-Time Monitoring | Rules | InTrust Internal Events rule folder.

These installation steps need to be done only once, no matter how many InTrust servers there are in the organization.

Next, configure the data source and rule that you have added.

To customize the configuration objects

1. Open the properties of the "Repository Status Monitoring" data source, go to the Parameters tab and configure the following parameters:

1. • Server Port
     The port to use for connecting to the InTrust server. If you left the default port during InTrust installation, you don't have to change this parameter.

1. • Status Type
     Which status to watch out for. The following values are supported:

1. • • RETENTION_EXPIRATION
       This is the default value; it means that in the queue of data to be forwarded some data has been marked for deletion and might be purged by retention policy.

1. • • RTC
       This status focuses on real-time collection errors such as those displayed in InTrust Deployment Manager for collections.

1. • • RETENTION_ENFORCEMENT
       This status means data marked for deletion because of excessive queue size has been purged. When this happens, an event is also written to the InTrust Server log.

2. Create a site and add a single InTrust server to it. One server is enough for this configuration.

3. Customize the properties of the "Repository Status Monitoring" rule if necessary. You may want to edit the alert message template on the Alert tab.

4. Create a real-time monitoring policy. In that policy, associate the site you have created with the rule you have configured. Enable the notifications you need and activate the policy.

After you have completed these steps, the rule begins watching all repositories in your organization.

If you want to monitor for multiple statuses, make a copy of the data source and a copy of the rule for each status you need, and use the corresponding data source copies in your rule copies. You can reuse your existing site and real-time monitoring policy for capturing the additional statuses.

If you get frequent alerts after setting up this monitoring workflow, consider changing the message retention settings. For that, edit the FORWARDING_RETENTION_EXPIRATION_PERIOD_SECONDS and FORWARDING_RETENTION_ENFORCEMENT_PERIOD_SECONDS organization parameters described in Fine-Tuning Forwarding with Organization Parameters.