[LOG4J2-435] Feature request: auto-delete older log files

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5
• Labels: Rollover
• Assignee: Remko Popma
• Reporter: Arkin Yetis
• Created: 20/Oct/13 03:44
• Updated: 30/Nov/16 17:07
• Resolved: 28/Nov/15 16:20

Description

Original description:

DefaultRolloverStrategy max attribute only applies if you have a %i in the file pattern. This request is to enhance DefaultRolloverStrategy or another appropriate component to allow a max number of files limit to apply across days/months/years when a filePattern includes a date pattern.

---

One of the most requested features is to add the ability to Log4j to "clean up" older log files. This usually means deleting these files, although it could also mean moving them to a different location, or some combination of these.

Users have different requirements for selecting the files to clean up. A common request is the ability to keep the last X number of log files. This works well if rollover is only date based but may give undesired results with size based rollover.

Another factor to consider is that the directory containing the log files may contain the log files for multiple appenders, or even files unrelated to logging.

Issue Links

• is duplicated by: LOG4J2-524 Feature request: auto-delete older rolled over files
• is duplicated by: LOG4J2-480 TimeBasedTriggeringPolicy with limited number of files
• is duplicated by: LOG4J2-656 How to delete rolled over folder older than six months.
• relates to: LOG4J2-35 Allow RollingFileAppender to do Rolling with a Date Pattern or DailyRollingFileAppender to have Max Backup Parameter
• relates to: LOG4J2-1198 Add support for custom rollover strategy
• relates to: LOG4J2-524 Feature request: auto-delete older rolled over files