This project came from a practical need: when database CPU rises, the question is usually not just whether the server is busy, but what is actually causing the pressure. DB CPU Monitor combines query digest summaries, table IO waits, active InnoDB transactions, and current sessions to make that easier to inspect.

There is a command-line flow for quick sampling and a local browser UI for reviewing reports, warnings, capability gaps, and saved snapshots. I like this project because it turns operational ambiguity into something more legible without pretending MySQL exposes perfect per-table CPU answers.