Let’s not conflate Spring Boot with Java. Besides the proliferation of numerous competing frameworks, there are plenty of use cases for smaller applications, too.
> On Sep 13, 2024, at 11:48, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > While this is nice I don’t think it will result in killing off logging > frameworks. While it supports the MDC it does not support structured messages. > > At the moment I don’t think it will support custom ContextDataProviders, but > that should come for free when I can get log4j-context-data completed. > > It also presumes you want all your ThreadContext keys included. We pass the > OAuth token in the ThreadContextMap and would not what that included as it is > huge and provides no value. > > At the moment to perform any customization you have to write your own > StructuredLogFormatter. The example they provide isn’t going to perform > particularly well which makes me wonder what the default implementation does. > > Ralph > >> On Sep 13, 2024, at 2:07 AM, Volkan Yazıcı <vol...@yazi.ci.INVALID> wrote: >> >> See the related release note >> <https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.4.0-M1-Release-Notes#structured-logging>. >> With this change, Spring Boot will effectively be providing an >> implementation-agnostic logging system abstraction featuring: >> >> - Level support >> - Pattern layout support >> - Structured (i.e., JSON) layout support (New!) >> >> Note that many modern SOA deployment solutions >> <https://logging.apache.org/log4j/2.x/soa.html> expect application logs to >> be written to the console, which renders the need for specialized appenders >> obsolete. Given this, if I may say, Spring Boot's logging abstraction >> pretty much makes the need to employ/configure a logging system obsolete – >> Spring Boot aims to cover 90% of logging-related use cases with its >> in-house abstractions. I can imagine a majority of its users will be able >> to develop and deploy to production without any `log4j2.xml`, >> `logback.xml`, or `logging.properties` configurations. >