Re: [PR] KAFKA-18831: Migrating to log4j2 introduce behavior changes of adjusting level dynamically [kafka]

[via GitHub]

chia7712 commented on PR #18969:
URL: https://github.com/apache/kafka/pull/18969#issuecomment-2673864688

   For future reference: Changing logger levels distinguishes between connector 
and admin APIs. The connector API uses "namespace"-based logger level changes, 
while the admin API uses specific logger-based changes.  Therefore, this PR 
uses `setLevel` for the core module and `setAllLevels` for the connect module.
   
   I have test the PR locally - see following screenshot
   
   ### case 0: changing root level does not impact other loggers
   
   ![螢幕快照 2025-02-21 
16-06-49](https://github.com/user-attachments/assets/b797b63e-6fd2-42c4-94af-cf397f7df1ee)
   
   ### case 1: the loggers defined by configs are not impacted by parent logger
    
   ![螢幕快照 2025-02-21 
16-09-46](https://github.com/user-attachments/assets/bf1ba447-2ff0-46a9-8d42-03e616bdaec8)
   


-- 
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: jira-unsubscr...@kafka.apache.org

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