wuzhanpeng commented on pull request #11993: URL: https://github.com/apache/pulsar/pull/11993#issuecomment-917793816
> This will only work for log4j, although it might not be the used logger. > > I think we should rely on the logger library to do this kind of operations. Log4j2 has already the option to monitor the log configuration file and update the settings. Thanks for your suggestions! As far as I know, `slf4j-1.X` currently does not support dynamically modify the log level, but this feature is hopefully implemented in `2.X`(see [this issue](https://jira.qos.ch/browse/SLF4J-124)). In addition, log4j natively supports jmx so that we can use mbeans to remotely monitor and control loggers, but it only supports the loggers predefined in the configuration file. With that in mind, this PR is dedicated to allow all loggers to log at a dynamic level avoiding the operation of modifying the configuration file and then restarting. -- 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]
