|
SERVER-70155 added a new metric "totalOplogSlotDurationMicros" in slow query messages. Would that be helpful here? Additionally, newer version of t2 has "oplog wt visibility lag" which is calculated as the gap between the timestamp of the latest oplog entry and the timestamp of the visibility point. But note that this is not exactly how long an oplog slot has been kept open. If no new oplog entry being written (i.e. latest oplog entry not changing), "oplog wt visibility lag" shown in t2 could be a constant. Would "totalOplogSlotDurationMicros" in slow query and "oplog wt visibility lag" in t2 together be sufficient?
|