[
https://issues.apache.org/jira/browse/FLINK-16793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068516#comment-17068516
]
Chesnay Schepler commented on FLINK-16793:
------------------------------------------
Are you not already able to do that? You can modify he log4j property files and
pass in the additional job.name property.
Baking this directly into the default properties files that Flink provides is
problematic since this only really makes sense in per-job deployments.
> Add jobName to log4j ConversionPattern
> --------------------------------------
>
> Key: FLINK-16793
> URL: https://issues.apache.org/jira/browse/FLINK-16793
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.10.0
> Reporter: jinhai
> Priority: Major
> Fix For: 1.11.0
>
>
> Add jobName to log4j, so we can search log by jobName on ELK.
> We can submit a job by add shell parameter：-yDjob.name=flink-test.
> And add ${job.name} to log4j pattern:
> log4j.appender.sls.layout.ConversionPattern=%d\{yyyy-MM-dd HH:mm:ss,SSS}
> ${job.name} %-5p %-60c %x - %m%n
> Then we can seach log by jobName on ELK or Graylog
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
