It just dawned on me as this topic was mentioned in a MySQL Conference presentation yesterday in a manual process. So my thought is, why can’t the following functionality be added to the MySQL server.
My request for two new extensions to the SHOW STATUS command.
SAVE STATUS – This enables the current SHOW STATUS to be saved (or more specifically cached), you can only keep one copy per server instance.
DIFF STATUS – This shows the difference between the current SHOW STATUS and the last saved show status from the SAVE STATUS command.
This would quickly, easily and interactively via a mysql prompt enable a DBA to see the state of change in a more condensed form. The syntax may need to cater for Session/Global scope, and of course would need to be appropiately named, my examples is just an idea.
Of course you can write an easy script that does the same, and provide a diff, but why not include it directly?
once the status variables are exposed via INFORMATION_SCHEMA, you will be able to just use regular tables and regular SQL commands to do this.
you could wrap all of it in a couple of stored procedures, even.