Adds a JSON formatter for the OTP kernel logger #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wday-contrib 2077
* Fixes badmatch with naked filename. * Fixes formatting that put commas around some colons. * Always uses this module's encoder for everything but binary escaping. * Allows inter-line delimiter to be configured. * Allows all top-level output keys to be filtered, not just metadata. * Handles format rewriting internally to exclude unused cases. * Expands test cases with verification on OTP 27+. wday-contrib 2077
* Handle pretty much any log event gracefully, no matter how misformed. * Fixed a unicode control character encoding bug that was just dumb. * All unicode, all the time. * Give reports with `args` and `format` fields special handling. * More eunit tests. wday-contrib 2077
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a standalone formatter to write properly-formed JSON records to log files.
While tested against Riak logs, it should work in any OTP application.
The formatter is thoroughly documented in the repo here
Important Note: When built with OTP-27+, the formatter uses the
jsonmodule for unicode escaping. On prior versions, it uses a less efficient but wholly self-contained mechanism. The macroUSE_OTP_JSONcan be defined at compile time to force use of of an existingjson:encode/1function if you know it is present in your application.