-
Notifications
You must be signed in to change notification settings - Fork 163
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
add net.logstash.log4j2.JSONEventLayoutV1 for log4j2 support #56
Conversation
michaelkuechler
commented
May 22, 2015
- moved HostData to new package as it seemed misplaced with the new log4j2 package
- moved HostData to new package as it seemed misplaced with the new log4j2 package
I noticed when using this. You'd loose the logging level because its always an empty map.
|
Hi Michael, Thanks for this ! I tried to reproduce this with your unit tests (net.logstash.log4j2.JSONEventLayoutV1Test) Are you actively using your patch ? |
I was to, but then priorities shifted 😐 - so I guess one has to look at the issue sometime… |
I fixed the issue with the log-level and discovered that your unit tests were using the log4j 1.x code. |
Will this PR be actioned and released anytime soon? The DNSBelgium fork appears to work. |
Hello, |
@cmpsoares91 as i wrote above: this is more than stale and AFAIR i never even ended up really using the code. so i consider this stale and probably outdated… |