Update the shipped log4j2 to use a File appender rather than a RollingFile appender. Simply log to a file, and expect logrotate (or other system tools) to manage log rotation, compression, etc.
A user alerted us to the /etc/logrotate.d/repose file not being owned by root (see linked ninja task) which prevents logrotate from working. The logrotate configuration we ship should be reasonable, and should work out-of-the-box alongside Log4j2.
The default log configuration just logs to a file. It does not rotate, compress, etc logs.
The default logrotate config is reasonable (rotates, compresses, etc).
The default logrotate config rotates logs.
Test to prove that log rotation occurs without issue.
Upgrade documentation makes it clear that:
The default logging config has changed.
Everyone should look at their logging config to make sure it fits for their specific API's needs.
This suggestion seriously applies to everyone whether or not they use the default config or have their own custom config.