[
https://issues.apache.org/jira/browse/ZOOKEEPER-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devarshi Shah updated ZOOKEEPER-4637:
-------------------------------------
Description:
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}
Apache Zookeeper 3.7.0 was using Log4j2 2.17.2; 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.
was:
We are changing the PatternLayout of log4j.properties to get the logs in custom
format:
{code:java}
appender.console.layout.pattern = {"timestamp":
"%d{yyyy-MM-dd'T'HH:mm:ss.SSSZ}", "severity": "%p{lowerCase=true}",
"service_id": "myKafka", "message": "%m"}%n {code}
Apache Zookeeper 3.7.1 is not allowing to change PatternLayout to manipulate
the logs format
> 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
> 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}
> Apache Zookeeper 3.7.0 was using Log4j2 2.17.2; 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)
