This continuous query for transaction matching is then followed by an ad-hoc query on the transaction window to identify which transactions were in-flight.
Knowing which transactions are in-flight is important for troubleshooting if the primary or replica system fails. In the event of failover, the Striim platform can replay the in-flight transactions to catch up the lagging systems. Also, transactions that are identified as in-flight can be pushed to a longer time window to see if they are resolved. If the transactions are matched during the longer time window, the alert is removed.
This solution works for one-way, as well as dual-active or multi-master replication.