ppkarwasz commented on issue #3100: URL: https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2895841889
@garydgregory, It seems we're very much aligned on the purpose of log levels: - **`ERROR` and `WARN`** should signal actionable issues. It's well known that not all `WARN` messages from the `StatusLogger` are truly actionable. While this is being addressed in [#1592](https://github.com/apache/logging-log4j2/pull/1592), I don’t currently have the bandwidth to review all `WARN` messages across the codebase. Any help on that front would be greatly appreciated. - **`TRACE` and `DEBUG`** are meant to provide verbose output and are mainly useful for Log4j developers or users troubleshooting specific problems. - **`INFO`** remains a perennial gray area. It should ideally communicate that the system is functioning correctly. But what qualifies as “reassuring” is subjective, and there will always be some disagreement here. > _"Regarding status logging in Log4j, I think we need to distinguish between what is informative and what is only useful during troubleshooting. That might help us demote some `INFO` messages to `DEBUG`."_ Here, I see things differently: we actually have very few events logged at the `INFO` level, and I believe we should consider **promoting** some important messages from `DEBUG`. For example: - Rollover events currently don't emit anything above `DEBUG`, even though they’re important for understanding log rotation behavior. - Network appenders should emit an `INFO` message when a connection is established. Unlike file-based appenders, network connectivity should never be assumed to “just work,” and an explicit log line can be very helpful. -- 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
