[
https://issues.apache.org/jira/browse/FLINK-30115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexis Sarda-Espinosa updated FLINK-30115:
------------------------------------------
Description:
Ussing logging processors/forwarders in Kubernetes is pretty common, and using
JSON format in logs can facilitate parsing, so it would be nice if the image
included the {{log4j-layout-template-json}} jar by default.
Alternatively, if users must create their own images for this, the classpath
for the operator must allow some customization.
It might even be valuable to separate the logging jars from the fat jar as it's
done for the Flink distribution.
was:
Ussing logging processors/forwarders in Kubernetes is pretty common, and using
JSON format in logs can facilitate parsing, so it would be nice if the image
included the {{log4j-layout-template-json}} jar by default.
Alternatively, if users must create their own images for this, the classpath
for the operator must allow some customization.
> Include log4j-layout-template-json jar in the default operator image
> --------------------------------------------------------------------
>
> Key: FLINK-30115
> URL: https://issues.apache.org/jira/browse/FLINK-30115
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.2.0
> Reporter: Alexis Sarda-Espinosa
> Priority: Major
>
> Ussing logging processors/forwarders in Kubernetes is pretty common, and
> using JSON format in logs can facilitate parsing, so it would be nice if the
> image included the {{log4j-layout-template-json}} jar by default.
> Alternatively, if users must create their own images for this, the classpath
> for the operator must allow some customization.
> It might even be valuable to separate the logging jars from the fat jar as
> it's done for the Flink distribution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
