Troubleshooting: Support for JSON formatted logs

[jinleileiking]

The current srs.log is in text format. Let's see if there is a need to output it as JSON. The company is quite supportive of providing feedback to the community. If you agree, I will mention it.

TRANS_BY_GPT3

[winlinvip]

Sorry, it is #2899 supporting Prometheus's API for troubleshooting implementation issues.

In troubleshooting, the main approach is to collect data through instrumentation like Prometheus, and then search for logs only when detailed logs are needed.

When searching for logs, the most suitable method is to use the grep command with the context ID. It is not suitable for JSON logs, but rather for text logs.

Generally, JSON-formatted logs are key logs for tracking, suitable for integration with Prometheus system, rather than directly converting all logs into JSON and filtering them.

Log troubleshooting is definitely necessary. I welcome discussing this solution and currently, I am more inclined towards using Prometheus with the current text log troubleshooting. Could you please look into it and see if it is suitable? I welcome your collaboration in implementing it.

TRANS_BY_GPT3