How to monitor MySQL / MariaDB query progress

For MySQL there are better ways to do this: <a href="https:&#x2F;&#x2F;mysql.wisborg.dk&#x2F;2018&#x2F;08&#x2F;10&#x2F;innodb-progress-information&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mysql.wisborg.dk&#x2F;2018&#x2F;08&#x2F;10&#x2F;innodb-progress-informat...</a><p>The article is MariaDB specific.

The shell script uses lsof to read file offsets of files. This is neat. But it won&#x27;t work for database tables in tablespaces (i.e. when not using file per table).

I’m not too sure if it covers table changes but MySQL comes with a slow log tool which tells you what queries are causing performance issues and if need be help optimize query requests itself, indexing even though is painstaking is perhaps the best way to fix the issue in the long run but to track down the slow queries in the first place and mitigate against them individually I’d use slow log.<p><a href="https:&#x2F;&#x2F;dev.mysql.com&#x2F;doc&#x2F;refman&#x2F;5.7&#x2F;en&#x2F;slow-query-log.html" rel="nofollow">https:&#x2F;&#x2F;dev.mysql.com&#x2F;doc&#x2F;refman&#x2F;5.7&#x2F;en&#x2F;slow-query-log.html</a>

Prometheus is a good option as well. <a href="https:&#x2F;&#x2F;github.com&#x2F;prometheus&#x2F;mysqld_exporter" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;prometheus&#x2F;mysqld_exporter</a>

Sorry but adding a new index on a table with 6 billion rows is stupid. If you did this in production, it would take that table offline for possibly days. And if it somehow failed, you would be SOL.<p>You create a copy of the table with an updated set of indexes and copy the data over into the new table. I think Percona even has a utility that will copy all the next data over via stored procedure that is getting written to the table.

I would love to see this built-in as a column to SHOW PROCESSLIST, that would show % done.