Data Monitoring / MySQL Monitoring
MySQL: MySQL counter resets
Rate charts show negative values after a server restart. Correlate server uptime and counter reset boundaries with collector samples.
Environment and inputs: MySQL 8.4 baseline; Performance Schema consumers, privileges and replication topology affect evidence availability.
Failure scenario
Rate charts show negative values after a server restart. Confirm the cause before choosing a fix.
Evidence to collect
Correlate server uptime and counter reset boundaries with collector samples. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Reset the rate baseline at discontinuities and preserve the restart as an annotated event. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for mysql counter resets 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.