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.
