You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/07/31 13:28:00 UTC

[jira] [Commented] (TINKERPOP-1983) Update Log4j to Log4j2

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

stephen mallette commented on TINKERPOP-1983:
---------------------------------------------

I did a quick look around on this and it's a bit of a mess to upgrade, plus spark/hadoop are still on the version we're on. I think the solution though to your specific problem is to just switch the logger out. We don't require you to use log4j, we just use it internally and package it for convenience in server and console zip distributions. All of our logging runs through slf4j, so you can just change out log4j for logback (which will support JSON as you'd like) - that's the exact use case for using slf4j in the first place. There's some discussion here on how to do this setup here:

https://gquintana.github.io/2017/12/01/Structured-logging-with-SL-FJ-and-Logback.html

will that work ok enough for me to close this?

> Update Log4j to Log4j2
> ----------------------
>
>                 Key: TINKERPOP-1983
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1983
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: build-release
>    Affects Versions: 3.3.3
>            Reporter: Florian Hockmann
>            Priority: Minor
>
> TinkerPop uses Log4j version 1.2.17 but Log4j 1 reached end of life almost three years ago:
> {quote}On August 5, 2015 the Logging Services Project Management Committee announced that Log4j 1.x had reached end of life.
> {quote}
> Source: [http://logging.apache.org/log4j/1.2/]
> It would be great if we could update to Log4j2 as it brings some nice benefits like new logging layouts for example (one of them is the JSON layout which is very useful to have to collect logs in something like the ELK stack or Graylog).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)