--- title: Summary of the Replica Monitor information description: Reference for the attributes in the PingDirectory Replica monitor entry, which tracks replica state for a specific base DN. component: pingdirectory version: 11.1 page_id: pingdirectory:pingdirectory_server_administration_guide:pd_ds_summary_replica_monitor_info canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectory_server_administration_guide/pd_ds_summary_replica_monitor_info.html llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: September 13, 2023 --- # Summary of the Replica Monitor information The following table provides a description of the attributes in the `cn=Replica` monitor entry for a specific base DN. The following is the distinguished name (DN) for the Replica Monitor server monitor entry. ``` dn: cn=Replica ,cn=monitor ``` | Monitor Attribute | Description | | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `base-DN: ` | Specified base DNThe monitor entries track your company's base DN or `base-DN: `,`dc=example,dc=com`, `cn=schema` `base-DN:` and `cn=topology,cn=config`. | | `connected-to: Replication Server ` | Replication port number and server ID of the replication server to which this LDAP Server is connectedThe first number is the replication server port number and the second number is the `server-id` of the replication server. | | `lost-connections` | Number of times the server has lost connection to a replication server | | `received-updates` | Number of updates that the server Replica has received from the connected replication server | | `sent-updates` | Number of updates sent to the replication server. | | `pending-updates` | Number of updates pending to send to the replication server. | | `replayed-updates` | Total number of updates from the replication server that have been replayed for this replica. | | `replayed-updates-ok` | Number of updates for this replica that have been successfully replayed with no conflicts. | | `replayed-update-failed` | Number of updates for this replica that were successfully replayed after automatically resolving a modify conflict. | | `resolved-modify-conflicts` | Number of updates for this replica that were successfully resolved after a modify conflict. | | `resolved-naming-conflicts` | Number of updates for this replica that were successfully resolved after a naming conflict. | | `unresolved-naming-conflicts` | Number of updates for this replica that could not be replayed because of an unresolvable naming conflict. | | `replica-id` | Server ID for this replica. | | `max-rcv-window` | Maximum number of changes that the server Replica can receive at a time before sending an acknowledgment back to the replication server. | | `current-rcv-window` | Current received window size for this replica. | | `max-send-window` | Maximum number of changes that the server Replica can send at a time to the replication server before requiring an ACK. | | `current-rcv-window` | Number of changes remaining to be received from the replication server before it must send an ACK. | | `max-send-window` | Maximum number of changes that the server Replica can send at a time to the replication server before requiring an ACK. | | `current-send-window` | Number of changes remaining to be sent to the replication server before requiring an ACK. | | `ssl-encryption` | Flag to indicate if SSL encryption is in use. | | `generation-id` | Generation ID for this suffix on the server. | | `replication-backlog` | Number of changes that are from this replica. |