Add Client interceptors for logging: logrus and zap #33
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.
This adds simple client-side interceptors for logging. For client side, the default mapping mostly consists of debug-level mapping.
Changes in general:
client_interceptor.go
to both logrus and zap, with fairly similar and simple semanticsclient_interceptor_test.go
to both logrus and zap, with very similar tests to the server sidespan.kind: server/client
to both logrus and zap server and client-side interceptors to be able to differentiate the log statements.@dackroyd @yifanzz