XDCR Metrics
A list of the metrics provided by XDCR.
The following XDCR metrics can be queried by means of the REST APIs described in Statistics.
See XDCR Metrics Cross Reference if you are looking for a metric name you know from an alternative supported or legacy tool.
Tip
|
Total number of documents filtered and not replicated because the documents were ATR documents |
Number of documents filtered that were binary documents |
Given the vBuckets of this node, the number of sequence numbers that need to be processed (either replicated or handled) before catching up to the high sequence numbers for the vBuckets |
Total number of documents filtered and not replicated because the documents were transaction client records |
Number of CRDs written to the conflict bucket. |
Number of conflict records filtered. |
Total number of conflict docs written. This counter includes all three types of conflict doc - source doc, target doc and CRD for the conflict detected. |
Number of EACCESS errors encountered while writing the conflict records to the conflict bucket. It is likely that something has gone wrong with the previliges of the user used for conflict writing |
Number of fatal errors encountered while writing the conflict records to the conflict bucket. It includes EINVAL and XATTR_EINVAL. |
Number of guardrail hit errors encountered while writing the conflict records to the conflict bucket. It includes resident ratio, data size and disk space guardrail errors. |
Number of docs which were identified as conflicts, but could not be logged because the conflict logger was hibernated. |
Number of errors which by design should not have been returned, encountered while writing the conflict records to the conflict bucket. It includes EEXISTS, ENOENT and LOCKED errors. |
Number of NOT_MY_VBUCKET errors encountered while writing the conflict records to the conflict bucket. It mostly is an indicator of topology changes. |
Number of network errors encountered while writing the conflict records to the conflict bucket. |
Number of unidentified errors encountered while writing the conflict records to the conflict bucket. One should turn on debug logging for the replication to catch the unknown response. |
Number of conflict records for which the conflict logger had trouble getting a connection to the conflict bucket. |
Number of docs which were identified as conflicts, but could not be logged because the logging queue was full. |
Number of source conflict docs written to the conflict bucket. |
Indicates if the conflict logger of the replication is running or hibernated or if it does not exist. |
Number of target conflict docs written to the conflict bucket. |
Number of conflict records which were throttled due to resource management and hence not written to conflict bucket. |
Number of TMPFAIL errors encountered while writing the conflict records to the conflict bucket. It indicates that the data service was temporarily busy and could not process the incoming write. |
Number of UNKNOWN_COLLECTION errors encountered while writing the conflict records to the conflict bucket. It indicates that where was a change to the collections setup which affected the conflict writes. |
Number of unknown responses returned by the source KV while writing the conflict records to the conflict bucket. One should turn on debug logging for the replication to catch the unknown response. |
Number of conflict records for which the write to conflict bucket was timed out. |
Amount of data replicated for a Replication |
Theoretical amount of data replicated for a Replication if compression were not used |
The total number of failed GET() operation on a reusable datapool within XDCR for the purpose of avoiding garbage generation |
The number of items sent by the Data Service waiting for the XDCR Source Nozzle to ingest and process |
The rolling average amount of time it takes for a document to be received by XDCR from the Data Service, to the time it is queued up in the Target Nozzle ready to be sent |
The number of times a Source Deletion or Expiration is cloned to be written to multiple Target Namespaces |
Number of Deletions written to Target |
Number of Deletions that failed Source-side Conflict Resolution |
Number of Deletions that failed Conflict Resolution at the Target |
Number of Deletions that were filtered Source-side |
Number of Deletions received from the Data Service |
Total number of documents not replicated because cas is beyond acceptable drift threshold |
Across vBuckets for this node, the sum of all sequence numbers that have been considered to be checkpointed |
Number of Source Document Mutation cloned to be written to different Target Namespaces |
Total number of documents whose compression was skipped before replication, due to a larger snappy-compressed size |
Number of documents (or tombstones) that were not replicated to the Target due to Conflict Resolution evaluated on the Source |
Number of documents failed Conflict Resolution at the Target |
Total number of documents filtered and not replicated due to the presence of transaction related xattrs in it |
Total number of documents filtered and not replicated because of user defined filter expressions |
Total number of documents filtered and not replicated due to any type of filtering |
Number of Documents Optimistically Replicated to the Target Cluster |
Number of Documents processed for a Replication |
Number of Document Mutations received from the Data Service |
The total number of documents that failed the set_with_meta operation due to the set CAS exceeding the acceptable threshold on the target data service. |
The total number of documents replicated to the target, where the target data service regenerated CAS values because the set CAS exceeded the acceptable threshold on the target's data service. |
The number of deletes issued using subdoc command instead of delete_with_meta to avoid cas rollback on target |
The number of sets issued using subdoc command instead of set_with_meta to avoid cas rollback on target |
Number of Document Mutations that couldn't be filtered due to inability to parse the document through Advanced Filtering engine and were not replicated |
Number of docs Document Mutations written/sent to the Target |
Number of Expirations written to the Target |
Number of Expirations that failed Source-side Conflict Resolution |
Number of Expirations that failed Conflict Resolution at the Target |
Number of Expirations filtered Source-side |
Number of Expirations or documents with TTL received from the Data Service |
Number of Document Mutations replicated that had the TTL changed to 0 before writing to Target (Source is unmodified) |
The number of writes that target rejected because each target data node is holding too much data |
The number of writes that target rejected because a data node is running out of disk space |
The number of writes that target rejected due to the target bucket being under the resident ratio threshold |
Number of mutations with HLV pruned when it is merged with target document |
Number of mutations with HLV pruned |
Number of mutations with HLV updated |
Number of mobile import mutations failed Source side Conflict Resolution. This is only counted in LWW buckets when enableCrossClusterVersioning is true |
Number of import mutations sent |
Total number of documents filtered and not replicated because the documents were mobile records |
The number of times checkpoint operation has completed successfully since this XDCR process instance is made aware of this replication |
The number of times checkpoint operation has encountered an error since this XDCR process instance is made aware of this replication |
The total number of replications that exists to replicate to a particular target cluster |
For a given source cluster, the number of data service nodes that it contains |
For a given source cluster, the total number of outbound replications to this cluster |
The number of currently present errors for a specific Replication Pipeline |
The pipeline status for a specific pipeline, where it could be paused, running or, error |
The rolling average amount of time it takes from when a MemcachedRequest is created to be ready to route to an outnozzle to the time that the response has been heard back from the target node after a successful write |
The number of seqno advance events received from source data service |
Number of Set operations successfully written to the Target |
Number of Set operations that failed Conflict Resolution at the Target |
Number of documents filtered that was of a DCP mutation |
Number of Sets received from the Data Service |
Amount of data being queued to be sent in a Target Nozzle |
Number of mutations with source mobile extended attributes removed |
The number of system events received from source data service |
The total number of EACCESS errors returned from the target node. |
Number of mutations with target mobile extended attributes preserved |
The total number of TMPFAIL errors returned from the target node. |
The total number of writes to target data service that returned with a status code that XDCR cannot comprehend |
The rolling average of the latency time introduced due to bandwith throttler |
The rolling average of the latency time introduced due to throughput throttler |
The rolling average amount of time it takes for a checkpoint operation to complete |
Number of true conflicts detected when the conflict logging feature is turned on. Logging of all these conflicts to a conflict bucket is best-effort, based on the system's state. |
The rolling average amount of time it takes for the source cluster to receive the acknowledgement of a SET_WITH_META response after the Memcached request has been composed to be processed by the XDCR Target Nozzle |
The rolling average amount of time it takes once a getMeta command is composed to be sent to the time the request is handled once the target node has responded |