We could always use markers for certain events, and then the default config could output those.
> On Aug 6, 2023, at 1:41 AM, Lukasz S. <lukasz.spy...@gmail.com> wrote: > > Hi, > > Just wanted to sum up proposed solutions and introduce new one: > > 1) Implemented default logger level change from ERROR to WARN (disliked by > Ralph and Gary) > > 2) logging an ERROR instead when JSON or YAML configuration is found but > dependencies are missing (proposed by Ralph) > > and thought of sth similar to no.2 but with introducing custom level below > ERROR at 150 (like "INIT_EVENT" or so). > Do not know the code well enough if it can be done without breaking > something, but just the idea. > > Łukasz. > > On 2023/07/26 10:14:00 "Piotr P. Karwasz" wrote: >> Hi all, >> >> In [1] Łukasz implemented the long-awaited bump of the default status >> logger level from ERROR to WARN. >> >> From my perspective this is a good change, since most configuration >> errors can be caught without setting `-Dlog4j2.debug=true`. On the >> other hand some users will complain that "working" configurations will >> start reporting errors on stderr now. >> >> What do you think about this? >> >> Piotr >> >> [1] https://github.com/apache/logging-log4j2/pull/1592 >>
