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

["Florian Hockmann (JIRA)" <ji...@apache.org>]

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

Florian Hockmann commented on TINKERPOP-1983:
---------------------------------------------

My motivation here was in this case simply that I wanted to use the JSON layout that is now included by default in Log4j2 but needs a third party library in Log4j 1. That isn't a big problem of course but it requires to manually copy the required jars and I think that needing a JSON layout is a frequent use case nowadays as most users probably use something like Graylog or the ELK stack to collect logs and make them searchable.

Also I would of course prefer if we wouldn't have to use a library that isn't maintained since 2015, but I have no idea how much effort such an upgrade would require as I'm not a Java developer. My understanding of logging in Java was that Logback defines the interface and Log4j is the implementation that could be replaced by any other implementation of Logback. So my hope was that it wouldn't require any code changes.

> 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)