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

ASF GitHub Bot commented on NUTCH-2885:
---------------------------------------

lewismc opened a new pull request #692:
URL: https://github.com/apache/nutch/pull/692


   PR for https://issues.apache.org/jira/browse/NUTCH-2885 ready for review.
   I feel that this simplifies the logging configuration with precise XML 
syntax... ultimately less code which I feel is readable.
   The configuration uses a RollingFileAppender with the cron triggering policy 
configured to trigger every day at midnight. Archives are stored in a directory 
based on the current year and month. All files under the base directory that 
match the `*/nutch-*.log.gz` glob and are 60 days old or older are deleted at 
rollover time. Additionally, we retain the ConsoleAppender configuration so 
everything is also written to STDOUT.
   I was motivated to work on this issue because I am performing a trade study 
which is evaluating [logz.io](https://logz.io/). Specifically, this will allow 
configuring nutch to use the 
[logzio-log4j2-appender](https://github.com/logzio/logzio-log4j2-appender).
   Comments welcome.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@nutch.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Upgrade to Log4j2
> -----------------
>
>                 Key: NUTCH-2885
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2885
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build, logging
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>             Fix For: 1.19
>
>
> log4j2 offers significant optimizations over log4j. I propose to upgrade. 
> This will NOT drop the use of slf4j... just upgrade the underlying logging 
> implementation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to