[
https://issues.apache.org/jira/browse/NUTCH-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378528#comment-17378528
]
ASF GitHub Bot commented on NUTCH-2885:
---------------------------------------
lewismc edited a comment on pull request #692:
URL: https://github.com/apache/nutch/pull/692#issuecomment-877705830
I've verified that this patch, with some minor additional configuration,
enables me to write logs locally, into logz.io and also into enterprise
instance of Splunk. The latter two really help with alerts and notifications if
something goes wrong i.e. ParseException.
--
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)
