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

embed: expose ZapLoggerBuilder #11147

Merged
merged 1 commit into from
Sep 13, 2019
Merged

Conversation

ChrisRx
Copy link
Contributor

@ChrisRx ChrisRx commented Sep 13, 2019

This exposes the ZapLoggerBuilder in the embed.Config to allow for
custom loggers to be defined and used by embedded etcd.

Fixes #11144

This exposes the ZapLoggerBuilder in the embed.Config to allow for
custom loggers to be defined and used by embedded etcd.

Fixes etcd-io#11144
@spzala
Copy link
Member

spzala commented Sep 13, 2019

/cc @gyuho

@gyuho gyuho merged commit bf3d1fb into etcd-io:master Sep 13, 2019
@gyuho
Copy link
Contributor

gyuho commented Sep 13, 2019

@spzala Can you help with backport?

gyuho added a commit that referenced this pull request Sep 13, 2019
…-upstream-release-3.4

Automated cherry pick of #11147
spzala added a commit to spzala/etcd that referenced this pull request Sep 13, 2019
@Quentin-M
Copy link
Contributor

I just created an issue suggesting exposing zap.Logger rather than zap.Config (which is pretty simple) so that a zapcore.Core wrap can be configured, allowing users to do advanced configurations to zap, including filtering of messages, generating metrics, etc. My use case is mostly being able to mute very noisey messages from clientv3 & embed selectively, while keeping a good log level. #12326

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.

embed: ZapLoggerBuilder no longer exposed
4 participants