Use this Knowledge Script to monitor the replication traffic from the DRA (Directory Replication Agent) between Active Directory sites, sometimes referred to as inter‑site replication traffic. This script raises an event if either the inbound bytes per second or the outbound bytes per second exceeds the threshold for the specified consecutive number of monitoring intervals.
This script gathers the following Windows performance counter values for use in data collection and threshold monitoring:
Performance Objects |
Counters |
---|---|
NTDS DirectoryServices |
DRA Inbound Bytes Compressed (Between Sites, After Compression)/sec DRA Outbound Bytes Compressed (Between Sites, After Compression)/sec NOTE:The same threshold applies to both counters. No computation applies. |
Active Directory domain controller
The default interval for this script is Every 3 hours.
Set the following parameters as needed:
Parameter |
How to Set It |
---|---|
General Settings |
|
Raise event if job fails |
|
Event severity when job fails |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the InterReplTraffic job fails. The default is 35. |
Monitor intersite replication traffic |
|
Event Notification |
|
Raise event when threshold exceeded too often? |
Select Yes to raise an event if the replication traffic threshold is exceeded too often. The default is Yes. |
Threshold -- Maximum inbound or outbound bytes per second |
Specify the maximum number of inbound or outbound replication bytes allowed per second before an event is raised. The default is 60000 bytes per second. Inbound bytes and outbound bytes per second are monitored separately and checked against this threshold. This script raises an event if either the inbound rate or the outbound rate exceeds this threshold more than n times. |
Maximum consecutive intervals threshold can be exceeded |
Specify the maximum number of consecutive intervals the inbound or outbound rate can be exceeded before raising an event. The default is 1 interval. Because replication traffic can have periodic spikes, consider setting this parameter to a higher value to filter out unnecessary events. For example, you can allow the inbound/outbound byte rate to exceed the threshold 3 to 4 times before an event is raised. |
Event severity when replication traffic exceeds threshold |
Set the severity level, from 1 to 40, to indicate the importance of an event in which replication traffic exceeds the threshold more than n times. The default is 20. |
Data Collection |
|
Collect data for inbound and outbound bytes per second? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of inbound bytes per second and the number of outbound bytes per second. The default is unselected. |