ruanwenjun opened a new issue, #10496: URL: https://github.com/apache/dolphinscheduler/issues/10496
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description When I do troubleshooting in master, I read the master's log, I find it is diffiicult to find out the whole log related to a specific workflowInstance or taskInstance. This is due to the process to execute a workflow is complex, and we didn't use a standard log format. In somewhere, we doesn't log the workflowInstanceId and does log the correct message. I suggest that we can add the WorkflowInstanceId and taskInstanceId(If present) in the log event begin, so that we can find the log belong to one specific WorkflowInstance. ``` [INFO] 2022-06-18 13:09:30.683 +0800 org.apache.xx:[100] WorkflowInstanceId-123-taskInstanceId-1: WorkflowInstance submit thread pool success. ``` This is just an example, or is there a better way to connect the log. ### Use case _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
