ppkarwasz commented on issue #3100: URL: https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2446579770
@morvael, > Ok, it seems I'm going through that code twice actually. And in the second one I'm doing code-based rebuild of configuration to configure some stuff in the code (this is for test programs) like in the old log4j. And I have the line there: `builder.setStatusLevel(Level.INFO);` ...so the funny thing is it must have not worked the same in old versions as it works now, because it didn't log those messages. That is easy to explain: I increased the level of those lifecycle messages in #3043 to make them more useful. The start and stop events of a `LoggerContext` and `Configuration` are pretty rare, but are very important to debug problems such as continuous reconfiguration. This is part of a continuous effort to improve our **own** logging statements according to our [log level semantic](https://logging.apache.org/log4j/2.x/manual/customloglevels.html#level-selection). The meaning of status logger levels should signify: * `ERROR`: these are errors that users should immediately resolve. * `WARN`: these are potential problems that the system detected (e.g. the presence of an unrecognized property in the configuration file) and users **should** be able to remove those warnings (currently it is not always possible, which is a blocker for #1592). * `INFO`: these are noteworthy events (e.g. reconfiguration, file rollover) that the system does not consider problems, but might help diagnosing problems. > Sorry for false report. No problem. -- 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]
