How to Exclude Lagged Database Copies from ENow

Problem

ENow is alerting on lagged database copies and you want to exclude them.

Excluding them takes two separate changes, because two different pages raise these alerts and each is suppressed a different way:

• The Queue and Copy Queue pages are excluded using a text file on the ENow web server.
• The Replication Health page is excluded using a monitoring exclusion in the Admin Console.

Doing only the first is the usual reason alerts continue after following this article — the text file has no effect on Replication Health.

Exclude from the Queue and Copy Queue pages

1. Create a text file named LaggedDatabase.txt.

2. Populate it line by line, one Database\Server pair per line:

   LaggedDatabase1\Server1
   LaggedDatabase2\Server2
   LaggedDatabase3\Server3

3. Place the file in the ENow Database folder. The default location is:

   C:\Program Files (x86)\ENow\MailscapeWeb\MailscapeData\Database

   

Exclude from the Replication Health page

1. Open the ENow Admin Console and navigate to Monitoring Policy > General > Monitoring Exclusions.

2. Enter the following exclusion in the Monitoring Exclusion field and click Save:

   *\ClusterHealth\dblogreplaykeepingup

   

With both changes in place, lagged database copy alerts are excluded across all three pages.

Applies to

ENow Management System versions 7.12.3.6858 and later.