ctubbsii commented on issue #3100: URL: https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2899363555
> * Rollover events currently don't emit anything above `DEBUG`, even though they’re important for understanding log rotation behavior. By rollover, do you mean reconfiguration, or file-rollover for the File appender? I came here because of the change in #3043, where the "Starting..." messages were changed from DEBUG to INFO in LoggerContext. I think these would still show up in a reconfiguration event, in addition to any also emitted by any appenders. I wouldn't want to see appenders log at INFO whenever they rollover to a new file because of a daily rollover or file size limit... that would be too noisy. > * 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. I'm not so sure. As a user, I wouldn't want to see those internals. I would want to see when the new config took effect from a particular network location, or a warning if there is a network timeout or other I/O error trying to reconcile a flaky connection. I would not want to see connection established messages, or downloaded file, or any of those intermediate steps to load the configuration at the designated network location. > DEBUG - Rotating file from A to B > INFO - Rotated file from A to B I think this is basically what I suggested. As a user who isn't currently troubleshooting anything, it's useful to know when the new config file took effect, but not the internals of what's happening before that point. The key here is that what goes to INFO should be a minimum. When a configuration is loaded or changed, only one INFO event is necessary... not a bunch coming from appenders, the LoggerContext, the root logger initialization, etc. Just one for the overall initialization of the configuration source, and just one each time the configuration changes. -- 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
