👋 We are deploying OSS version (0.50.16) via Helm and am seeing a log of “debug” logs coming from various part of the system, is there a way to turn them off? Sample log:

2023-08-28 21:59:15 DEBUG i.g.n.s.i.n.u.i.l.AbstractInternalLogger(log):214 - [id: 0xa6ed0cd9, L:/172.30.49.61:40972 - R:airbyte-temporal/10.100.113.23:7233] INBOUND WINDOW_UPDATE: streamId=0 windowSizeIncrement=68

Thanks!

Yes, you can control the level of logging in Airbyte by setting the

LOG_LEVEL

environment variable. By default, it might be set to

DEBUG

, which is why you're seeing a lot of debug logs. You can change it to

INFO

,

WARN

,

ERROR

, or

FATAL

to reduce the amount of logs. Here's how you can set it when deploying with Docker:

bash LOG_LEVEL=INFO docker compose up

Please replace

INFO

with your desired log level. Note that this command is just an example, you might need to adjust it according to your actual deployment command. For more information, you can refer to the [Airbyte documentation](https://docs.airbyte.com/contributing-to-airbyte/developing-locally#inspecting-the-messages-passed-between-connectors) and this [support conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1672170451301579) on Slack. However, please note that the information provided is based on the extracts given and might not cover all the details of your specific situation. If you're still having trouble, I recommend checking the official Airbyte documentation or reaching out to the Airbyte community for more specific guidance.

That i have tried, but didn’t work. i’m guessing this log could be coming from some library (temporal?) that is not connected to this

LOG_LEVEL

env var….

I have the same issue. LogLevel is set to INFO, but still a lot of DEBUG logs in my Docker logs. @Shangwei Wang have you found a solution?

Nope. We are planning to stop ingesting/filtering out these logs to our logging infra.