[
https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029807#comment-15029807
]
Robert Schaft commented on LOG4J2-435:
--------------------------------------
Please look at
[my Post from two days
ago|https://issues.apache.org/jira/browse/LOG4J2-435?focusedCommentId=15026538&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15026538].
I proposed there a FileAggregationBasedDeletion that contains an
AggregationSet, an ordering element and a deletionTrigger element.
The deletionTrigger Element could than contain multiple Accumulated elements.
It is interesting that you ask about what I would expect. That means it is not
clear from the element names even if used the names proposed by you.
Apparently I was wrong criticizing the amount of elements required for the
configuration (<Or>, <And>, <AnyOf>...). To avoid ambiguity, you need to allow
at most one root filter within the delete element. The combining filters
"AnyOf" or "AllOf" (which allow more than one filter child element) make than
clear how the filters are combined.
Btw: The beauty of the "trigger"-term is from my point of view, that it makes
indirectly clear that any of the "...Trigger" could fire. So they are logically
OR connected but all feeded at the same time (no {code:java}&&{code} shortcut
operator).
> Feature request: auto-delete older log files
> ---------------------------------------------
>
> Key: LOG4J2-435
> URL: https://issues.apache.org/jira/browse/LOG4J2-435
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Arkin Yetis
> Assignee: Remko Popma
> Labels: Rollover
> Fix For: 2.5
>
> Attachments: LimitingRolloverStrategy.java, SizeParser.java
>
>
> Original description:
> {quote}
> 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.
> {quote}
> ----
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
