e code does not directly refer to it.
> logback.qos.ch
>
>
> Regards,
> Alexis.
>
>
> From: houssem
> Sent: Wednesday, September 1, 2021 7:02 PM
> To: user@flink.apache.org
> Subject: Re: logback variable substitution in kubernetes
&g
n logger
exists by virtue of its declaration in the configuration file - even if the
Java source code does not directly refer to it.
logback.qos.ch
Regards,
Alexis.
From: houssem
Sent: Wednesday, September 1, 2021 7:02 PM
To: user@flink.apache.org
Subject: Re:
Yes i did it all
when i hard code the log level and the file name everything works fine
but when i try to use variables , they won't be replaced.
On 2021/09/01 11:43:21, Yang Wang wrote:
> Did you have removed the log4j related jars in the $FLINK_HOME/lib
> directory?
> Refer to the docume
Did you have removed the log4j related jars in the $FLINK_HOME/lib
directory?
Refer to the documentation[1] for how to use logback.
[1].
https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/advanced/logging/#configuring-logback
Best,
Yang
houssem 于2021年9月1日周三 下午5:00写道：
> Yes
Yes i did this verification and i have all environment variables.
On 2021/09/01 06:09:27, Yang Wang wrote:
> From the logback documentation[1], it could support OS
> environment substitution.
> Could you please check that the environment variables have been properly
> set?
> Maybe you could tunn
>From the logback documentation[1], it could support OS
environment substitution.
Could you please check that the environment variables have been properly
set?
Maybe you could tunnel into the Kubernetes pod via "kubectl exec" and do
such verification.
Best,
Yang
houssem 于2021年8月31日周二 下午7:28写道：
