Bug #91697 Improve dedicated log file for InnoDB monitor
Submitted: 18 Jul 2018 12:13 Modified: 4 Mar 2020 13:44
Reporter: Przemyslaw Malkowski Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:5.7+ OS:Any
Assigned to: CPU Architecture:Any
Tags: InnoDB monitor, innodb-status-file

[18 Jul 2018 12:13] Przemyslaw Malkowski
Currently we can have InnoDB monitor logging automatically to the error log via innodb_status_output variable, which makes the error log fat and difficult to read when looking for other things.

Other way is to enable innodb-status-file, which however has two important limitations:
 - the variable is not dynamic
 - the innodb_status.PID file gets overwritten on each status update, hence we don't have a history

How to repeat:
Enable innodb_status_output or innodb-status-file

Suggested fix:
Allow the InnoDB monitor to log to a dedicated separate file, which will be appended same way asit currently works with error log.
[4 Mar 2020 13:44] MySQL Verification Team
Hi Mr. Malkowski,

Thank you for your feature request.

Your request makes sense to me.

Verified as reported.