v3rpc: Log expensive request in UnaryInterceptor #12086
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
recently, In the process of troubleshooting the etcd request timeout, I encountered the following problems:
Adjusting the log level to debug can solve the above problems, but the production environment needs to be changed
and performance will drop sharply.
This pr will print expensive request information in grpc interceptor to solve the above problems and improve the efficiency of the troubleshooting.