-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Request for comments about a LTSV encoder #253
Comments
Awesome - I'm glad to hear that zap was useful for you! I haven't worked with the LTSV encoding before - from the docs, I can see that it's accepted by a variety of logging tools. Are you aware of any common software that emits LTSV logs by default? I'm going to defer this until after the 1.0 release, since the encoder API is changing (though nearly all the code you have should still work, it'll just require some find&replace updates). Once we've released 1.0, I'll take a closer look at your code and figure out whether we should include it in zap itself. |
Thanks for your kind words. Apache config example:
nginx config example:
Also, with Fluentd | Open Source Data Collector | Unified Logging Layer, you can convert logs in other formats to LTSV using Text Formatter Overview | Fluentd. I understand that you defer this pull request after zap 1.0 release. Thanks! |
Closing this issue, since there's no active work to do in zap. |
Sorry for being late. I noticed your mention yesterday. |
First of all, thanks for a nice logging library for Go!
I created a Labeled Tab-separated Values (LTSV) encoder for zap.
https://github.com/hnakamur/zap-ltsv
Could you take a look and give some comments to issues?
Thanks for your time in advance.
The text was updated successfully, but these errors were encountered: