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.
