Good point. log4j2-logstash-layout <https://github.com/vy/log4j2-logstash-layout> does indeed provide full schema customization and better performance. Though it can achieve this due to the fact that it only focuses on JSON. In the case of JsonLayout, the default Log4j 2 JSON layout, it is a simple extension over AbstractJacksonLayout, which further provides XmlLayout and YamlLayout. Hence from a maintainability point of view, Log4j's approach make sense. That said, LogstashLayout can indeed be integrated into Log4j as a successor to JsonLayout. One also need to note that having a separate project for the plugin gives a flexible release schedule freedom, which I took advantage a lot.
On Mon, May 13, 2019 at 10:49 PM Ralph Goers <ralph.go...@dslextreme.com> wrote: > Just one concern here. If this is a better JSON Layout implementation than > what Log4j provides why hasn’t it been contributed to the project? > > Ralph > > > On May 13, 2019, at 1:40 PM, Volkan Yazıcı <volkan.yaz...@gmail.com> > wrote: > > > > Motivated by Matt's e-mail, I also would like to share my submission for > > the ApacheCon Europe 2019 <https://aceu19.apachecon.com/>. Fingers > > crossed... > > > > *How and why of the fastest Log4j JSON layout* > > Log4j is awesome. Love it or hate it, it is the de facto logger in the > Java > > land. In the era of microservices, where hundreds of applications running > > on thousands of nodes spitting out logs at rates exceeding gigabytes per > > second, the output is not an easily navigable text file anymore, but a > > structured river fed by smaller streams and navigated on giant cruise > ship > > looking dashboards. People further hack this battle tested tools into IoT > > event streaming pumps with demanding throughput requirements. I will walk > > you through how bol.com (the biggest e-commerce platform in the > Netherlands > > and Belgium) had a need for a new Log4j JSON layout plugin. I will > further > > explain how people started using it outside bol.com and this motivated > it > > to be the fastest among all its competitors. Enjoy logging? Suffer from > > JSON battle scars? Have an inclination for garbage-free Java code? Then > we > > have a story you might want to hear. > > >
