-
Notifications
You must be signed in to change notification settings - Fork 15
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
Decoder needs parsers for Logger name, thread name etc #4
Comments
Any hope of this being sorted? |
I'm a bit preoccupied, but I'll look into it this weekend. |
tony19
added a commit
that referenced
this issue
Jul 22, 2013
tony19
added a commit
that referenced
this issue
Jul 22, 2013
tony19
added a commit
that referenced
this issue
Jul 22, 2013
tony19
added a commit
that referenced
this issue
Jul 22, 2013
I've added parsers for the following fields:
While unit tests exist for these fields, there might be some test cases I've missed. Feel free to create issues for them (and patches/pull-requests would be much appreciated). The following fields are not [yet] parsed:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the
Decoder
class, common fields in log messages are not parsed into theLoggingEvent
unless parsers are defined. e.g.The
LoggerNameParser
andThreadParser
are faily simple. e.g.trim()
is needed - not sure whyHope this helps
Michael
The text was updated successfully, but these errors were encountered: