[
https://issues.apache.org/jira/browse/FLINK-26328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora reassigned FLINK-26328:
----------------------------------
Assignee: Matyas Orhidi
> Control Logging Behavior in Flink Deployments
> ---------------------------------------------
>
> Key: FLINK-26328
> URL: https://issues.apache.org/jira/browse/FLINK-26328
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Matyas Orhidi
> Assignee: Matyas Orhidi
> Priority: Major
>
> Looking at
> [https://github.com/spotify/flink-on-k8s-operator/blob/master/docs/user_guide.md#control-logging-behavior]
>
> Something similar could work here as well
> {quote}The default logging configuration provided by the operator sends logs
> from JobManager and TaskManager to {{{}stdout{}}}. This has the effect of
> making it so that logging from Flink workloads running on Kubernetes behaves
> like every other Kubernetes pod. Your Flink logs should be stored wherever
> you generally expect to see your container logs in your environment.
> Sometimes, however, this is not a good fit. An example of when you might want
> to customize logging behavior is to restore the visibility of logs in the
> Flink JobManager web interface. Or you might want to ship logs directly to a
> different sink, or using a different formatter.
> You can use the {{spec.logConfig}} field to fully control the log4j and
> logback configuration. It is a string-to-string map, whose keys and values
> become filenames and contents (respectively) in the folder
> {{/opt/flink/conf}} in each container. The default Flink docker entrypoint
> expects this directory to contain two files: {{log4j-console.properties}} and
> {{{}logback-console.xml{}}}.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
