You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@yazi.ci> on 2024/01/22 12:29:55 UTC
Re: [log4j] Bump default status logger level to WARN
Piotr, could you share some examples of typical working configurations that
will start reporting errors? What kind of errors will these reports
contain? A message or a fully-blown stack trace? Will there be a multitude
of these? Or 1-2 occasional appearances?
I know answers will vary dependending on the configuration. I am interested
in, let's say, typical Spring, Java application users with simple
`log4j2.xml`, `log4j2.yaml` files.
On Wed, Jul 26, 2023 at 12:14 PM Piotr P. Karwasz <pi...@gmail.com>
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
>
Re: [log4j] Bump default status logger level to WARN
Posted by Matt Sicker <ma...@musigma.org>.
I like this idea, Piotr.
> On Jan 22, 2024, at 12:28 PM, Piotr P. Karwasz <pi...@gmail.com> wrote:
>
> Hi Volkan,
>
> On Mon, 22 Jan 2024 at 15:15, Volkan Yazıcı <vo...@yazi.ci> wrote:
>> Shall we mention this issue (that is, ineffective configurations as the one
>> you shared about `bufferSize`-vs-`bufferedIo`) to Łukasz and see if he
>> would be willing to carry out that clean up? ... granted PMC agrees to
>> raise the default status logger level to WARN.
>
> The task to silence excessively verbose warnings can require quite a
> lot of knowledge of Log4j code internals.
> I prefer to do it myself and ask another PMC member to proofread it.
>
> Piotr
Re: [log4j] Bump default status logger level to WARN
Posted by "Piotr P. Karwasz" <pi...@gmail.com>.
Hi Volkan,
On Mon, 22 Jan 2024 at 15:15, Volkan Yazıcı <vo...@yazi.ci> wrote:
> Shall we mention this issue (that is, ineffective configurations as the one
> you shared about `bufferSize`-vs-`bufferedIo`) to Łukasz and see if he
> would be willing to carry out that clean up? ... granted PMC agrees to
> raise the default status logger level to WARN.
The task to silence excessively verbose warnings can require quite a
lot of knowledge of Log4j code internals.
I prefer to do it myself and ask another PMC member to proofread it.
Piotr
Re: [log4j] Bump default status logger level to WARN
Posted by Volkan Yazıcı <vo...@yazi.ci>.
I am in favor of reporting unrecognized/ignored properties, otherwise there
is no incentive for users to fix their configurations. Those who don't want
to be bothered with them, can still do so via
`-Dlog4j.StatusLogger.level=off`.
Shall we mention this issue (that is, ineffective configurations as the one
you shared about `bufferSize`-vs-`bufferedIo`) to Łukasz and see if he
would be willing to carry out that clean up? ... granted PMC agrees to
raise the default status logger level to WARN.
On Mon, Jan 22, 2024 at 2:34 PM Piotr P. Karwasz <pi...@gmail.com>
wrote:
> Hi Volkan,
>
> On Mon, 22 Jan 2024 at 13:31, Volkan Yazıcı <vo...@yazi.ci> wrote:
> > Piotr, could you share some examples of typical working configurations
> that
> > will start reporting errors? What kind of errors will these reports
> > contain? A message or a fully-blown stack trace? Will there be a
> multitude
> > of these? Or 1-2 occasional appearances?
>
> There are about 100 warnings in `log4j-core`. Most of them only occur
> if an error condition occurs, but it is fixed by the code.
> For example if a user has a properties configuration with a lot of
> unrecognized/ignored properties, a warning will be issued for each one
> of them.
>
> Some of these warnings are not fixable by the user, e.g. the "The
> bufferSize is set to {} but bufferedIo is false: {}" (bufferSize has
> always a value), but I am willing to go through the list of warnings
> and fix them.
>
> Piotr
>
Re: [log4j] Bump default status logger level to WARN
Posted by "Piotr P. Karwasz" <pi...@gmail.com>.
Hi Volkan,
On Mon, 22 Jan 2024 at 13:31, Volkan Yazıcı <vo...@yazi.ci> wrote:
> Piotr, could you share some examples of typical working configurations that
> will start reporting errors? What kind of errors will these reports
> contain? A message or a fully-blown stack trace? Will there be a multitude
> of these? Or 1-2 occasional appearances?
There are about 100 warnings in `log4j-core`. Most of them only occur
if an error condition occurs, but it is fixed by the code.
For example if a user has a properties configuration with a lot of
unrecognized/ignored properties, a warning will be issued for each one
of them.
Some of these warnings are not fixable by the user, e.g. the "The
bufferSize is set to {} but bufferedIo is false: {}" (bufferSize has
always a value), but I am willing to go through the list of warnings
and fix them.
Piotr