rawlinp opened a new issue #6533: URL: https://github.com/apache/trafficcontrol/issues/6533
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Router ## Current behavior: <!-- Describe how the current features are insufficient. --> The current log4j2 config causes TR to rename `access.log` to `access.log.2022-01-30-30` (for example) then recreate the `access.log` file. This can cause data loss problems for log forwarding tools that expect to tail the same log file without having it change out from underneath them. ## New behavior: <!-- Describe how this change would improve Traffic Control --> TR's log4j2.xml config should use a rollover strategy that doesn't cause the log file to be renamed then recreated. I _think_ this can be accomplished with a `DirectWriteRolloverStrategy` which is documented [here](https://logging.apache.org/log4j/2.x/manual/appenders.html#DirectWriteRolloverStrategy). However, in order to limit the number of rolled-over log files on disk, we may need to combine that with a custom delete action which is documented [here](https://logging.apache.org/log4j/2.x/manual/appenders.html#CustomDeleteOnRollover). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
