When logging master/slave servers, it can be nice to see what is replication lag over the time, and for example - look what happens after a large UPDATE query.
"SHOW SLAVE STATUS" can used to find other problems, over the time (like broken replication)
I like this product and used It for more than 3 years. Thanks!
thank you for the suggestion. Agreed, replication lag when a heavy update is issued is a very interesting scenario.
It could probably be auto-configured as well, meaning it would only run on slave servers, not on masters. If SHOW SLAVE STATUS returns an empty result, that profiling will be disabled from then on. So no additional load will be placed on the server.