Bug #114343 mysqlsh.log include os pid
Submitted: 14 Mar 2024 2:41 Modified: 13 Sep 2024 9:57
Reporter: Mike Griffin Email Updates:
Status: Closed Impact on me:
None 
Category:Shell General / Core Client Severity:S4 (Feature request)
Version:8.0.36 OS:Linux
Assigned to: CPU Architecture:Any
Tags: mysqlsh

[14 Mar 2024 2:41] Mike Griffin 
Description:
It would be easier to use tools like grep if the running client included the OS pid of the client

How to repeat:
After repeated attempts to use util.dumpInstance and util.loadDump, and particularly when more than one client are running, it is difficult to discern relevant log entries. 

Suggested fix:
Something like:

    time_t timestamp{time(nullptr)};
    pid_t os_pid;
    std::string_view domain;
    std::string_view message;
    LOG_LEVEL level{LOG_LEVEL::LOG_NONE};
[14 Mar 2024 6:20] MySQL Verification Team 
Hello Mike Griffin,

Thank you for the reasonable feature request!!

regards,
Umesh
[13 Sep 2024 9:57] Edward Gilmore 
Posted by developer:
 
Added the following note to the MySQL Shell 9.1.0 release notes:
  
The MySQL Shell log format has been updated to include the process (PID) and thread ID (TID).

Thank you for the bug report.