logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files
Date Thu, 03 Dec 2015 16:18:11 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038015#comment-15038015
] 

Ralph Goers commented on LOG4J2-435:
------------------------------------

The only difference with what we are doing in general is that you would specify:
{code}
<Delete baseDir="${sys:base}" maxDepth="2">
  <ScriptCondition>
    <Script language="groovy">groovy script goes here</Script>
  </ScriptCondition>
</Delete>
{code}

{code}
<Delete baseDir="${sys:base}" maxDepth="2">
  <ScriptCondition>
    <ScriptFile path="path/to/my/script.groovy">
  </ScriptCondition>
</Delete>
{code}

or

{code}
<Scripts>
  <ScriptFile path="path/to/my/script.groovy" name="deleteScript" isWatched="true"/>
</Scripts>

<Delete baseDir="${sys:base}" maxDepth="2">
  <ScriptCondition>
    <ScriptRef ref="deleteScript">
  </ScriptCondition>
</Delete>
{code}

Note that the Script, ScriptFile and Scripts elements are already implemented. The only thing
Remko needs to do is implement the ScriptCondition element. The ScriptCondition can be implemented
to call the script for each file and return true or false as to whether it should be deleted,
or it could be implemented to pass the script a list of all the files and expect the script
to return those that should be deleted.

> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message