Monitoring replication

This section covers how to use the PingDirectory server to monitor replication.

The PingDirectory server monitors replication in the following ways:

Use the dsreplication tool with the status subcommand to display basic information about the replicated base distinguish names (DNs), the number of entries replicated, as well as the approximate size of replication backlogs at each PingDirectory server.
Obtain more detailed information about the state of replication through the information exposed in its monitoring framework under cn=monitor.
Use Periodic Stats Logger plugin, which allows collecting replication statistics for profiling server performance. For more information, see Profiling Server Performance Using the Periodic Stats Logger.

Administrators can monitor their replication topologies using several tools and protocols:

The PingDataMetrics Server
SNMP
LDAP
JMX
The administrative console. For more information, see Managing Logging and Managing Monitoring.

Monitoring replication using cn=monitor

The cn=monitor branch has several entries that store the replication state of a topology.

`cn=monitor` branch entries and their descriptions
cn=monitorentries	Description
Direct LDAP Server `<baseDN><host name:port><serverID>`	Defines an LDAP server that directly connects to the replication server you are querying. The information in this entry applies to the replication server local to the `cn=monitor` entry. For more information, see Summary of the Direct LDAP Monitor information.
Indirect LDAP Server `<baseDN><serverID>`	Defines an LDAP server that connects to another replication server in the topology. While this server connects to the same topology, it does not connect to the replication server you are querying. For more information, see Summary of the Indirect LDAP Server Monitor information.
Remote Repl Server `<baseDN><host name:port><serverID>`	Defines a remote replication server that connects to the local replication server. Information in this entry is in respect to the Replication Server local to the `cn=monitor` branch. For more information, see Summary of the Remote Replication Server Monitor information.
Replica `<baseDN>`	Stores information for an instance of the replicated naming context, also known as the replica, with respect to the PingDirectory server and its communication with a replication server. The replica information sends and receives changes from the replication servers. For more information, see Summary of the Replica Monitor information.
Replication Server	Shows information specific to the Replication Server running. For more information, see Summary of the Replication Server Monitor information.
Replication Server Database `<baseDN><serverID>`	Shows information for the changelog table of replica (suffix) in the replication server. As the Replication Server receives updates from the PingDirectory server, it records those changes in the changelog table. For more information, see Summary of the Replication Server Database Monitor information.
Replication Server Database Environment	Shows information for the database environment for the replication server backend as well as the total number of records added to and deleted from the database. For more information, see Summary of the Replication Server Database Environment Monitor information.
Replication Summary `<baseDN>`	Shows summary information on the replication topology and the state for a particular base distinguish name (DN). For more information, see Summary of the Replication Summary Monitor information.
replicationChanges Backend	Shows the backend information for all replication changes. For more information, see Summary of the replicationChanges Backend Monitor information.
Replication Protocol Buffer	Shows the state of the buffer (initially 4k) for protocol operations, which is stored in thread local storage. For more information, see Summary of the Replication Protocol Buffer Monitor information.