Logging configuration determines which messages an application records, their severity threshold, and how and where those messages are written. It helps developers collect enough detail to investigate a problem without overwhelming the logs or harming maintainability. section 4.2.2
A Log4j configuration connects three components:
- The logger selects messages, such as messages from a package or messages at or above a configured severity. section 4.2.2
Enable finer-grained investigation
With the root logger set to info, an extractor records its start and result but omits debug messages for each parsed character. Changing the root level to debug adds those character-level observations without recompiling the application. Do not confuse this level with the status attribute on Configuration: level controls application messages, while status reports Log4j's own events. section 4.2.2
