ppkarwasz commented on PR #3658:
URL: https://github.com/apache/logging-log4j2/pull/3658#issuecomment-2976250721
Hi @anindita-sarkarArray,
I discussed this with @garydgregory, and I agree that the `toString()`
methods should remain unchanged to preserve a better debugging experience
within IDEs.
Following the discussion in #3100, I also think it's a good idea to reduce
verbosity in Log4j Core by default. With that in mind, I propose the following:
1. **Downgrade the log level of the `INFO` messages** I added in
`LoggerContext` and `AbstractConfiguration` to `DEBUG`, with one exception:
* Keep the `INFO` message at:
https://github.com/apache/logging-log4j2/blob/422c385dc9450d4f620a23d84abe2d6a0aa5b9fb/log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java#L328-L334
2. **Add an `INFO` message in
`LoggerContext.setConfiguration(Configuration)`** to notify users when a new
configuration becomes active (i.e., after the `updateLoggers()` call). The
message could be formatted like:
```
<logger_context_class_name>[name=<name>] is using
<configuration_class_name>[location=<location>, lastModified=<last_modified>].
```
Let me know what you think.
--
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
