Data Monitoring / MySQL Monitoring
MySQL: Seconds behind source limitations
A lag indicator is zero while the business still sees stale replica data. Compare receiver state, applied positions and a known source transaction watermark.
Environment and inputs: MySQL 8.4 baseline; Performance Schema consumers, privileges and replication topology affect evidence availability.
Failure scenario
A lag indicator is zero while the business still sees stale replica data. Confirm the cause before choosing a fix.
Evidence to collect
Compare receiver state, applied positions and a known source transaction watermark. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Use multiple freshness signals rather than relying on one lag field. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for seconds behind source limitations using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.