Hi All,
How to extend the log rotation time for request.log and access.log for 2 days.
The default is "'.'yyyy-MM-dd" (daily log rotation) and if we want it for two days once log rotation?
Thanks,viki
Solved! Go to Solution.
Hi
I was reading this article, see if this could help you
Link:- http://sling.apache.org/documentation/development/logging.html
The rolling schedule is specified by setting the org.apache.sling.commons.log.file.size
property to a java.text.SimpleDateFormat
pattern. Literal text (such as a leading dot) to be included must be enclosed within a pair of single quotes. A formatted version of the date pattern is used as the suffix for the rolled file name. Internally the Log bundle configures a TimeBasedRollingPolicy
for the appender. Refer to TimeBasedRollingPolicy for more details around the pattern format
For example, if the log file is configured as /foo/bar.log
and the pattern set to '.'yyyy-MM-dd
, on 2001-02-16 at midnight, the logging file /foo/bar.log
will be renamed to /foo/bar.log.2001-02-16
and logging for 2001-02-17 will continue in a new /foo/bar.log
file until it rolls over the next day.
It is possible to specify monthly, weekly, half-daily, daily, hourly, or minutely rollover schedules.
DatePattern | Rollover schedule | Example |
---|---|---|
'.'yyyy-MM | Rollover at the beginning of each month | At midnight of May 31st, 2002 /foo/bar.log will be copied to /foo/bar.log.2002-05 . Logging for the month of June will be output to /foo/bar.log until it is also rolled over the next month. |
'.'yyyy-ww | Rollover at the first day of each week. The first day of the week depends on the locale. | Assuming the first day of the week is Sunday, on Saturday midnight, June 9th 2002, the file /foo/bar.log will be copied to /foo/bar.log.2002-23 . Logging for the 24th week of 2002 will be output to /foo/bar.log until it is rolled over the next week. |
'.'yyyy-MM-dd | Rollover at midnight each day. | At midnight, on March 8th, 2002, /foo/bar.log will be copied to /foo/bar.log.2002-03-08 . Logging for the 9th day of March will be output to /foo/bar.log until it is rolled over the next day. |
'.'yyyy-MM-dd-a | Rollover at midnight and midday of each day. | at noon, on March 9th, 2002, /foo/bar.log will be copied to /foo/bar.log.2002-03-09-AM . Logging for the afternoon of the 9th will be output to/foo/bar.log until it is rolled over at midnight. |
'.'yyyy-MM-dd-HH | Rollover at the top of every hour. | At approximately 11:00.000 o'clock on March 9th, 2002, /foo/bar.log will be copied to /foo/bar.log.2002-03-09-10 . Logging for the 11th hour of the 9th of March will be output to /foo/bar.log until it is rolled over at the beginning of the next hour. |
'.'yyyy-MM-dd-HH-mm | Rollover at the beginning of every minute. | At approximately 11:23,000, on March 9th, 2001, /foo/bar.log will be copied to /foo/bar.log.2001-03-09-10-22 . Logging for the minute of 11:23 (9th of March) will be output to /foo/bar.log until it is rolled over the next minute. |
I hope this would help you.
Thanks and Regards
Kautuk Sahni
why do you need at 2 days once !!
You can usually do a daily rotation neither a rotation based on size if you dont want daily.
Views
Replies
Total Likes
Hi
I was reading this article, see if this could help you
Link:- http://sling.apache.org/documentation/development/logging.html
The rolling schedule is specified by setting the org.apache.sling.commons.log.file.size
property to a java.text.SimpleDateFormat
pattern. Literal text (such as a leading dot) to be included must be enclosed within a pair of single quotes. A formatted version of the date pattern is used as the suffix for the rolled file name. Internally the Log bundle configures a TimeBasedRollingPolicy
for the appender. Refer to TimeBasedRollingPolicy for more details around the pattern format
For example, if the log file is configured as /foo/bar.log
and the pattern set to '.'yyyy-MM-dd
, on 2001-02-16 at midnight, the logging file /foo/bar.log
will be renamed to /foo/bar.log.2001-02-16
and logging for 2001-02-17 will continue in a new /foo/bar.log
file until it rolls over the next day.
It is possible to specify monthly, weekly, half-daily, daily, hourly, or minutely rollover schedules.
DatePattern | Rollover schedule | Example |
---|---|---|
'.'yyyy-MM | Rollover at the beginning of each month | At midnight of May 31st, 2002 /foo/bar.log will be copied to /foo/bar.log.2002-05 . Logging for the month of June will be output to /foo/bar.log until it is also rolled over the next month. |
'.'yyyy-ww | Rollover at the first day of each week. The first day of the week depends on the locale. | Assuming the first day of the week is Sunday, on Saturday midnight, June 9th 2002, the file /foo/bar.log will be copied to /foo/bar.log.2002-23 . Logging for the 24th week of 2002 will be output to /foo/bar.log until it is rolled over the next week. |
'.'yyyy-MM-dd | Rollover at midnight each day. | At midnight, on March 8th, 2002, /foo/bar.log will be copied to /foo/bar.log.2002-03-08 . Logging for the 9th day of March will be output to /foo/bar.log until it is rolled over the next day. |
'.'yyyy-MM-dd-a | Rollover at midnight and midday of each day. | at noon, on March 9th, 2002, /foo/bar.log will be copied to /foo/bar.log.2002-03-09-AM . Logging for the afternoon of the 9th will be output to/foo/bar.log until it is rolled over at midnight. |
'.'yyyy-MM-dd-HH | Rollover at the top of every hour. | At approximately 11:00.000 o'clock on March 9th, 2002, /foo/bar.log will be copied to /foo/bar.log.2002-03-09-10 . Logging for the 11th hour of the 9th of March will be output to /foo/bar.log until it is rolled over at the beginning of the next hour. |
'.'yyyy-MM-dd-HH-mm | Rollover at the beginning of every minute. | At approximately 11:23,000, on March 9th, 2001, /foo/bar.log will be copied to /foo/bar.log.2001-03-09-10-22 . Logging for the minute of 11:23 (9th of March) will be output to /foo/bar.log until it is rolled over the next minute. |
I hope this would help you.
Thanks and Regards
Kautuk Sahni
This was requirement for Project team, and just wanted to see if it is possible.. We are doing log rotation based on size.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies