vy commented on PR #1592:
URL: https://github.com/apache/logging-log4j2/pull/1592#issuecomment-1904116163

   @lukaszspyra, I am sorry for the delay. There were more pressing issues. As 
a part of our ongoing effort to clean up the `log4j-api` in `2.x`, we are 
re-visiting the idea of decreasing the default `StatusLogger` level from 
`ERROR` to `WARN`. PMC is mostly concerned about the noise this will create for 
existing users.
   
   Once the default level is set to `WARN`, some warnings will start getting 
displayed on unrecognized/ignored properties. This is good. OTOH, there will 
also appear some not much useful warnings, e.g., `The bufferSize is set to ... 
but bufferedIo is false`. **Would you be interested in fixing these (e.g., 
lowering the level of such messages to `INFO` or conditionally enabling them)** 
and adding that your PR? I believe we (@ppkarwasz?) can provide assistance for 
such an effort. PMC needs to be convinced anyway. But if their _"logging 
noise"_ concerns are addressed, I don't expect a blocker from that direction.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to