Open mjtrangoni opened 6 months ago
relevant issues about unexpected log level precedence, relating to config.json
file:
Shawn noted that the config.json
file is only important for Windows, and that we should ignore it on Linux. I'd be OK with that since the only time I need to think about it on Linux is when I'm deleting it work around the log level precedence issue.
Shawn wrote in https://github.com/openziti/ziti-tunnel-sdk-c/issues/461#issuecomment-1198620116
As of now this notion of a "config file" should not be processed by ziti-edge-tunnel on Linux.
IMHO, log level works as expected. The issue here is more about the error log which should not be triggered running in a container. If this is a windows thing, maybe it helps handling this case for != windows.
@scareything any news on this? Due to the livenessProbe this issue logs two errors every minute.
@scareything this is still active with 0.22.32, and produce a lot of unnecessary logs.
Hi @qrkourier @scareything,
I am starting to upgrade the ziti-edge-tunnel image to the latest version via helm (0.22.23), and it seems that the new livenessProbe implemented here via command
ziti-edge-tunnel tunnel_status
is logging some errors and warnings every minute!See,
IMHO, the ERROR should be handled by the tunnel gracefully, so that it does not get triggered at all. And the resulting warning messages at the end could also be saved if possible.
I look forward to hearing your thoughts. Thank you!