fix: correct example to avoid zerolog fields combined #569
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.
I follow the current code in the example of using
zerolog
andfields
grown after each request. It combines allfields
to the context ofl
after each request and makes the log messages become huge.It's the same with this issue on
zap
#559I fixed this by creating a new instance of
zerolog.Logger
instead of usingl
and it works like a charm.Changes
interceptors/logging/examples/zerolog
Verification
I tested and it works on my project, logs work fine and didn't get combined
fields