Data Monitoring / MySQL Monitoring
MySQL: Statement digest ranking
A query with low average time dominates total database work. Compare digest execution counts, total latency and per-call latency.
Environment and inputs: MySQL 8.4 baseline; Performance Schema consumers, privileges and replication topology affect evidence availability.
Failure scenario
A query with low average time dominates total database work. Confirm the cause before choosing a fix.
Evidence to collect
Compare digest execution counts, total latency and per-call latency. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Reduce repeated work or call frequency while keeping slow outlier analysis separate. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for statement digest ranking 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.