When performance related to Active Directory degrades, PI_AD records can be collected and monitored to help resolve issues. The following describes the items monitored to identify bottlenecks when various problems occur:
The following explains monitoring examples for when the above problems occur. Note that these monitoring examples are for reference, and might differ depending on the user environment. Adjust the thresholds and other settings to suit the user environment.
When the domain controller load is constantly high
High load on a domain controller is often due to frequent disk access by the Active Directory database. In this case, the issue can be resolved by revising the memory cache or buffer allocation.
Table 3-9 Fields monitored for database cache usage
Field | Description |
---|---|
Cache % Hit | The percentage of database file page requests performed without incurring file operations, by using the database cache. |
Cache Page Fault Stalls/sec | The number of page faults per second for which service could not be received, because there was no page allocated from the database cache. |
Cache Page Faults/sec | The number of database file page requests per second required because the database cache manager allocated a new page from the database cache. |
Cache Size | The amount of system memory used to maintain information frequently used by the database cache manager from database files. |
Table Open Cache % Hit | The percentage of database tables opened using cached schema information. |
Table Open Cache Hits/sec | The number of database tables opened per second using cached schema information. |
Table Open Cache Misses/sec | The number of database tables opened per second without using cached schema information. |
Table Opens/sec | The number of database tables opened per second. |
Table 3-10 Fields for monitoring the status of database log writes
Field | Description |
---|---|
Log Record Stalls/sec | The number of log records per second that could not be added per second due to lack of log buffer space. |
Log Threads Waiting | The number of threads standing by for writing log buffer data to log files, while waiting for database update to complete. |
Log Writes/sec | The number of times per second that log buffer data is written to log files. |
When logins are concentrated on a specific domain
Check the following fields to determine the number of sessions currently being used due to Active Directory.
Table 3-11 Fields for monitoring the number of current sessions
Field | Description |
---|---|
AB Client Sessions | The number of client sessions for the connected address book. |
LDAP Client Sessions | The number of session for the connected LDAP client. |
When intrasite network load is high
Intrasite network load might be high because Active Directory is performing large-scale replication within the site. The following table lists the fields for monitoring intrasite replication.
Table 3-12 Fields for monitoring intrasite replication traffic
Field | Monitoring target | Description |
---|---|---|
DRA In Not Compress | Inbound replication | The number of bytes for uncompressed data (amount of input). |
DRA In Not Compress/sec | The number of bytes per second for uncompressed data (input frequency). | |
DRA Out Not Compress | Outbound replication | The number of bytes for uncompressed data (amount of output). |
DRA Out Not Compress/sec | The number of bytes per second for uncompressed data (output frequency). |
When network load between sites is high
The network load between sites might be high because Active Directory is performing large amount of replication between sites. Unlike intrasite replication, communication for replication between sites involves compression. The replication operation itself does not change. The following fields are for monitoring replication traffic between sites.
Table 3-13 Fields for monitoring replication traffic between sites
Field | Monitoring target | Description |
---|---|---|
DRA In After Compress | Inbound replication | The number of bytes for compressed data (amount of input). |
DRA In After Compress/sec | The number of bytes per second for compressed data (frequency of input). | |
DRA In Before Compress | The number of bytes for uncompressed data (amount of input). | |
DRA In Before Compress/sec | The number of bytes per second for uncompressed data (frequency of input). | |
DRA Out After Compress | Outbound replication | The number of bytes for compressed data (amount of output). |
DRA Out After Compress/sec | The number of bytes per second for compressed data (frequency of output). | |
DRA Out Before Compress | The number of bytes for uncompressed data (amount of output). | |
DRA Out Before Compress/sec | The number of bytes per second for uncompressed data (frequency of output). |