Latency monitoring means executing the rs_ticket command at the primary database, retrieving the latency data from the replicate database, and storing the results in the SAP Control Center repository.
rs_ticket gathers time information at various points in the replication path as it flows from the primary database to the replicate database. You can then use this latency information to identify bottlenecks in the replication path. Latency information helps ensure that data is flowing efficiently between the primary and replicate databases.
The latency monitoring process collects data on a specified schedule for each replicate Replication Server and for the primary Replication Server for the path you configured. The primary collection executes the rs_ticket command in the primary database. Each replicate collection performs a collection in all its paths. When a path collection occurs, the results of the rs_ticket command are retrieved from the replicate database, stored in the repository, and displayed in the latency history chart in the Replication Server Monitor's Paths view or in the Replication Path Dashboard for server performance monitoring.
Each collection repeats until the end date or until you manually stop the latency monitoring process. Once the process is stopped, all collections are deleted from the scheduler.