Hi Neha,
The maxHistory denotes the number of history files that are maintained. So if you want a cap of the index to be say 10, configure the maxHistory to 10 like shown below, which results in the max index of the history files will be 10.
In your case it will be test.log.2011-04-06.10
Thanks,
Kalyan
From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of Neha Kothari
Sent: Wednesday, April 06, 2011 9:27 AM
To: logback users list
Subject: Re: [logback-user] Logback configuration
The max history is for setting the limit on the file size. I want to set a cap on the index i appended.
Clemens Siebler <clemens.siebler@googlemail.com> 04/06/2011 05:08 AM
|
|
Should be possible using the maxHistory parameter:
<appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender">
<File>test.log</File>
<encoder>
<pattern>... </pattern>
</encoder>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>test.log.%d{yyyy-MM-dd}.%i</fileNamePattern>
<maxHistory>10</maxHistory>
<timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
<maxFileSize>10MB</maxFileSize>
</timeBasedFileNamingAndTriggeringPolicy>
</rollingPolicy>
</appender>
On Tue, Apr 5, 2011 at 10:22 PM, Neha Kothari <neha.kothari@db.com> wrote:
Hi have started to use logback for logging in java. I am using "TimeBasedRollingPolicy" rolling policy as I wanted dated logs.
My file pattern looks like c:/spg-live.%d{yyyy-MM-dd}.%i.log
Is there a way that I can put a maxIndex (i.e the maximum limit for i) using the same rolling policy?
Thanks
---
This communication may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this communication
in error) please notify the sender immediately and destroy this
communication. Any unauthorized copying, disclosure or distribution of the
material in this communication is strictly forbidden.
Deutsche Bank does not render legal or tax advice, and the information
contained in this communication should not be regarded as such.
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user
---
This communication may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this communication
in error) please notify the sender immediately and destroy this
communication. Any unauthorized copying, disclosure or distribution of the
material in this communication is strictly forbidden.
Deutsche Bank does not render legal or tax advice, and the information
contained in this communication should not be regarded as such.