ctubbsii commented on issue #5453: URL: https://github.com/apache/accumulo/issues/5453#issuecomment-2794949508
@ppkarwasz wrote: > What output did you expect to get by setting the level of the [status logger](https://logging.apache.org/log4j/2.x/manual/status-logger.html) to `INFO`? I believe it was just reloading information when the file changed. > Before version `2.24.0` there were barely any `INFO` messages in Log4j code, In version `2.24.0` I tried to add at least: I think that's what we liked about it. The stuff in there was rare, and relevant. > * when a configuration starts and stops. > * when a reconfiguration event occurs. I'd have to check, but I thought there was already some information for reconfiguration in there prior to the recent changes. I think I found those useful, but the recent changes not so useful. > **Note**: for a "smooth sailing" I would not recommend `WARN` either. Theoretically it should contain only potentially problematic conditions that users should be able to fix by modifying their configuration file. Unfortunately there is still to work to do and some warnings can not be "fixed" by users. For this reason the default is `ERROR` (see [apache/logging-log4j2#1592](https://github.com/apache/logging-log4j2/pull/1592) and related issues). If there are any issues with noisy WARN, we haven't been impacted, to the best of my knowledge. (Unless there are new ones added recently). > > > ``` > > 2025-04-04T19:10:16.058147325Z pool-10-thread-1 INFO Stopping configuration org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@18765d9b... > > 2025-04-04T19:10:16.058147313Z pool-9-thread-1 INFO Stopping configuration org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@18f5f66d... > > 2025-04-04T19:10:16.058631896Z pool-10-thread-1 INFO Configuration org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@18765d9b stopped. > > 2025-04-04T19:10:16.058880638Z pool-9-thread-1 INFO Configuration org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@18f5f66d stopped. > > ``` > > Admittedly this is mostly garbage. Yep. That's why it'd be better if these were put in DEBUG. > > As an excuse I might add that the `PropertiesConfiguration` was a standalone sample project that went viral and was added to Log4j 2 Core _vox populi_. We rarely use `*.properties` ourselves. I opened [apache/logging-log4j2#3599](https://github.com/apache/logging-log4j2/issues/3599) to fix `toString()` method of `PropertiesConfiguration`. While a better `toString()` would make the messages more useful, I still think they should be at DEBUG, as they are just too noisy and not useful for normal usage. We were happy before the messages were added, and will be happy with them present at DEBUG, but invisible to us watching INFO. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
