Suggestion for go-zero Logging Functionality

[zhaozuowu]

Description:
During my usage of go-zero, I noticed that the logging of input and output parameters is primarily recorded in a single content field using path and method. This approach can be limiting, especially when troubleshooting issues in production.

Problem:
1：Current logging methods record path, method, code, request, and response to the content string text, not to a json structure, which allows you to use tools like ELK, according to path, method, code, and code. The input or output becomes very difficult to retrieve, as shown in Figure 1

2:In complex API debugging and issue resolution, having a JSON structure would significantly enhance the ability to perform field-based full-text searches, improving troubleshooting efficiency.

Suggestion:
I would like to suggest enhancing the go-zero logging feature to support recording input and output, as well as method, path, code parameters as JSON structures. This will allow developers to more efficiently analyze logs and troubleshoot problems, similar to Figure 2, which is the result of our revamp of the go-zero log

Thank you for your hard work and support!