Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

etcdserver: automated cherry pick of #9990 to release-3.3 #10004

Conversation

jingyih
Copy link
Contributor

@jingyih jingyih commented Aug 15, 2018

Cherry pick of #9990 on release-3.3.

#9990: etcdserver: add grpc interceptor to log info on incoming

Jingyi Hu added 3 commits August 14, 2018 16:20
…etcd server

To improve debuggability of etcd v3. Added a grpc interceptor to log
info on incoming requests to etcd server. The log output includes
remote client info, request content (with value field redacted), request
handling latency, response size, etc. Uses zap logger if available,
otherwise uses capnslog.

Also did some clean up on the chaining of grpc interceptors on server
side.
Rebased to master PR etcd-io#9994.  Fixed a Go format issue in
v3rpc/interceptor.go.  Updated vendor to include go-grpc-middleware.
Code clean up in interceptor.go
@gyuho
Copy link
Contributor

gyuho commented Aug 15, 2018

I don't think we want to backport zap dependencies to release-3.3?

@gyuho
Copy link
Contributor

gyuho commented Aug 15, 2018

Oh never mind. We already had zap in 3.3 branch.

Copy link
Contributor

@gyuho gyuho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@gyuho gyuho merged commit f8fc923 into etcd-io:release-3.3 Aug 15, 2018
@jingyih
Copy link
Contributor Author

jingyih commented Aug 15, 2018

Thanks Gyuho!

@jingyih jingyih changed the title Automated cherry pick of #9990 etcdserver: automated cherry pick of #9990 to release-3.3 Aug 18, 2018
@jingyih jingyih deleted the automated-cherry-pick-of-#9990-origin-release-3.3 branch September 7, 2019 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants