Re: [log4j] Bump default status logger level to WARN

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. wrote: > > Hi, > > Just wanted to sum up proposed solutions and introduce new one: > > 1) Implemented default logger level change from ERROR to WARN (dislike

Log4j2's Automatic Configuration is great, but there is a bit ambiguity (in doc)

Hi, This online doc: Log4j – Configuring Log4j 2 (apache.org) describes “Automatic Configuration”: “ Log4j has the ability to automatically configure itself during initialization. When Log4j starts it will locate all the Configur

Re: [log4j] Bump default status logger level to WARN

I commented on the PR. It seems odd that the discussion is continuing on the dev list instead of the PR, but OK. The PR reports a problem with a specific condition that is essentially logging at the wrong log level. It proposes a fix of changing the default log level. I see no need to do that.

Re: [PR] Document dependency upgrades for 2.20.1 (logging-log4j2)

For deps, these could be called "updates". Gary On Mon, Aug 7, 2023, 2:27 PM ppkarwasz (via GitHub) wrote: > > ppkarwasz commented on PR #1591: > URL: > https://github.com/apache/logging-log4j2/pull/1591#issuecomment-1668387324 > >@vy, > >I split all the updates into separate changelog

Re: [log4j] Bump default status logger level to WARN

Discussions on PRs or issues would be easier to continue if the same mailing lists weren’t already spammed by Dependabot. > On Aug 7, 2023, at 1:08 PM, Ralph Goers wrote: > > I commented on the PR. It seems odd that the discussion is continuing on the > dev list instead of the PR, but OK. > >