Database systems and related replication monitoring methods

A method of monitoring a replication service replicating data from a source database system to a destination database system, the method comprising:

• periodically inserting, at the source database system, a plurality of tracking entries into one or more logs of database transactions at the source database system, wherein the replication service is configurable to replicate the one or more logs of database transactions to the destination database system;
• receiving, at the destination database system from the replication service, a first subset of database transactions of the one or more logs of database transactions at the source database system, wherein the first subset of database transactions includes one or more tracking entries of the plurality of tracking entries;
• detecting, at the destination database system, an anomaly associated with replicating the data from the source database system in response to an absence of receiving, from the replication service, a subsequent subset of database transactions of the one or more logs of database transactions at the source database system that includes an expected tracking entry within a threshold period of time after receiving the one or more tracking entries;
• and
• initiating a remedial action in response to detecting the anomaly.

A computing device comprising:

• at least one non-transitory machine-readable storage medium that stores software;
• and
• at least one processor, coupled to the at least one non-transitory machine-readable storage medium, to execute the software that implements a replication monitoring service and that is configurable to:
• determine an expected tracking entry expected to be received from a replication service over a network based on one or more tracking entries in a first set of database transactions at a source database system received from the replication service, wherein the first set of database transactions comprises a subset of one or more logs of database transactions at the source database system and the one or more tracking entries are inserted into the one or more logs of database transactions;
• detect a replication anomaly in response to an absence of receiving, from the replication service, a subsequent set of database transactions at the source database system that includes the expected tracking entry within a threshold period of time;
• and
• initiate a remedial action in response to detecting the anomaly.