ppkarwasz commented on PR #3719:
URL: https://github.com/apache/logging-log4j2/pull/3719#issuecomment-2954785747

   The normalization logic in `StatusLogger` only needs to support the five 
legacy constants listed below and their corresponding normalized forms. There's 
no need for complex logic or performance optimizations here — defining four 
simple lookup tables to map between the different formats should be sufficient.
   
   | Legacy Constant                      | Normalized Forms                    
         |
   
|--------------------------------------|----------------------------------------------|
   | `log4j2.debug`                       | Normal: `log4j2.debug`              
          |
   |                                      | Env Var: `LOG4J_DEBUG`              
          |
   |                                      | Log4j 3: `log4j.debug`           |
   | `log4j2.status.entries`              | Normal: `log4j2.statusEntries`      
         |
   |                                      | Env Var: `LOG4J_STATUS_ENTRIES`     
         |
   |                                      | Log4j 3: 
`log4j.statusLogger.statusEntries`  |
   | `log4j2.StatusLogger.level`          | Normal: `log4j2.statusLoggerLevel`  
         |
   |                                      | Env Var: 
`LOG4J_STATUS_LOGGER_LEVEL`         |
   |                                      | Log4j 3: `log4j.statusLogger.level` 
         |
   | `log4j2.StatusLogger.dateFormat`     | Normal: 
`log4j2.statusLoggerDateFormat`      |
   |                                      | Env Var: 
`LOG4J_STATUS_LOGGER_DATE_FORMAT`   |
   |                                      | Log4j 3: 
`log4j.statusLogger.dateFormat`     |
   | `log4j2.StatusLogger.dateFormatZone` | Normal: 
`log4j2.statusLoggerDateFormatZone`  |
   |                                      | Env Var: 
`LOG4J_STATUS_LOGGER_DATE_FORMAT_ZONE` |
   |                                      | Log4j 3: 
`log4j.statusLogger.dateFormatZone` |
   


-- 
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

Reply via email to