[
https://issues.apache.org/jira/browse/ZOOKEEPER-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved ZOOKEEPER-4637.
--------------------------------------
Assignee: Chris Nauroth
Resolution: Information Provided
Hello [~TheDevarshiShah],
Sorry, I'm not aware of a way to get this functionality directly from reload4j.
I think you'll need to keep swapping in Log4J 2 if you want this capability. If
it helps, see [GitHub
PR#1793|https://github.com/apache/zookeeper/pull/1793#pullrequestreview-857545860],
where I left instructions on how to do this.
At this point, the ZooKeeper community is committed to Reload4J in the 3.7
release line and Logback in the 3.8 release line. We can review patches to
upgrade those libraries if they offer new releases with more capabilities in
the future.
> Apache Zookeeper 3.7.1 is not allowing to change PatternLayout to manipulate
> the logs format
> --------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-4637
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4637
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.7.1
> Reporter: Devarshi Shah
> Assignee: Chris Nauroth
> Priority: Major
>
> We are using the PatternLayout of log4j.properties to get the logs in custom
> format in our Apache Zookeeper cluster:
> {code:java}
> appender.console.layout.pattern = {"timestamp":
> "%d{yyyy-MM-dd'T'HH:mm:ss.SSSZ}", "severity": "%p{lowerCase=true}",
> "message": "%m"}%n {code}
> To fix logging related critical vulnerabilities we have uplifted to log4j2 in
> Apache Zookeeper 3.7.0; though, the Apache Zookeeper 3.7.1 is using Reload4j
> 1.2.19 which is based on Log4j1 1.2.17. So for us, it's downgrade from Log4j
> 2.17.2 to 1.2.17. We've tried to modify the PatternLayout accordingly, but it
> didn't work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
