I’ve delayed answering because I can’t make up my mind. I am still thinking about this.
Ralph > On Feb 12, 2024, at 12:58 PM, Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > > Hi Volkan, > >> On Mon, 12 Feb 2024 at 20:30, Volkan Yazıcı <vol...@yazi.ci> wrote: >> `StatusLogger` can be configured in following ways: >> >> 1. Passing system properties to the Java process (e.g., >> `-Dlog4j2.StatusLogger.level=INFO`) >> 2. Providing properties in a `log4j2.StatusLogger.properties` file in >> the classpath >> 3. Using Log4j configuration (i.e., `<Configuration status="WARN" >> dest="out">`) in a `log4j2.xml` in the classpath. This is facilitated by >> `StatusConfiguration`. >> 4. Programmatically (i.e., `StatusLogger.getLogger().setLevel(...)`) > > You missed some of the possibilities: > > 5. Setting `log4j2.debug` effectively switches the status logger from > ERROR to TRACE. Before Volkan's PR #2249 this was the only way to > debug problems that occur before a configuration is found and loaded: > `log4j2.StatusLogger.level` was a NO-OP, > 6. The property `log4j2.defaultStatusLevel` sets the default value of > the "status" property of a configuration. > > I support the idea of removing the "status" property from the > configuration. We could reintroduce it later, but only after we figure > out how to set the logging level separately from components of > different configurations. > > Piotr
