You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Robert P (Jira)" <ji...@apache.org> on 2019/08/26 17:59:00 UTC
[jira] [Created] (LOG4J2-2682) TimeBasedTriggeringPolicy
Robert P created LOG4J2-2682:
--------------------------------
Summary: TimeBasedTriggeringPolicy
Key: LOG4J2-2682
URL: https://issues.apache.org/jira/browse/LOG4J2-2682
Project: Log4j 2
Issue Type: New Feature
Affects Versions: 2.12.0
Reporter: Robert P
In this configuration setup:
{code:xml}
<RollingRandomAccessFile name="ThisLog"
fileName="path/to/logs/ThisLog.log"
filePattern="path/to/logs/ThisLog_%d{yyyy.MM.dd_hh.mm.ss.sss}.log"
append="true">
<Policies>
<TimeBasedTriggeringPolicy interval="1" />
</Policies>
{code}
I think the interval in *TimeBasedTriggeringPolicy* could be revamped.
I want to be able to print the timestamp on each log file; however, I don't want to have to do the math to estimate when an exception might occur then calculate the average timing for a new day.
I feel it should be configurable to such extent like
{code:xml}
<TimeBasedTriggeringPolicy interval="1d" />
{code}
Like...
||Interval type||Pattern||
|Day|d|
|Month|M|
|Week|w|
|Hour|h|
|Minute|m|
|Second|s|
|etc.| |
--
This message was sent by Atlassian Jira
(v8.3.2#803003)