rolling-file | Write to a file until limits | Proxy library

According to Serilog, you would need to use file logging – as it seems, RollingFile might be going away soon.

Important note: the rolling functionality in this sink has been improved and merged into the Serilog.Sinks.File package. RollingFile will be maintained for the foreseeable future, however File is recommended for new applications.

Here is a straightforward way of using a File Sink:

appsettings.json

1) You need to set a logging.file or logging.path property, not both.
So logging.file=/path/to/log/folder/myLog should be enough to get a myLog log file in the specified path.

The spring boot documentation mentions that.

2) This is the format pattern for the log rolling, not for the current log :

Please set additivity=false for both named loggers.

Also, add a root logger configuration to tell Log4j2 where to send the logging calls other than the “file1” and “file2” loggers:

According to this post TimeBasedRollingPolicy does not work with MaxBackupIndex.

But you could use the TimeAndSizeRollingAppender. It has a Log file rollover by time or date, Maximum file size and a Maximum number of backup files parameter.

I don't think there is a log4j appender which observes the total directory size. It seems to me that this is more a housekeeping job and not one for a logger. Not even logrotate which is more generic that a log appender offers a directory size limit. You could use an external script (eg. triggered by cron) which does directory cleanup like that.