I see I can set the scheduler, server, and worker log level in the helm chart, can i do the same for sync jobs? I'm having issue with the source pod just deciding to close things down half way through and it's not recording why.

Hey you would have the logs of the sync they are not helping? Also anything on the kube side?

As far as I can tell, the source connector just closes the database connection pool mid-sync with no message why recorded anywhere (kube or sync log). It then exits with code 1, which is of course reported later in the sync logs 🙂 I posted some initial logs here: https://airbytehq.slack.com/archives/C01MFR03D5W/p1646115911718059?thread_ts=1646115690.504409&cid=C01MFR03D5W And later discovered how to set log levels, so here is one when I set log levels to debug. (By setting all the

log.level

entries and adding a

JOB_DEFAULT_ENV_LOG_LEVEL

extra environment variable to all the places I could, which I confirmed added

LOG_LEVEL=DEBUG

to the

source-mysql-sync-*

pods main container)

@Gary K keep messages in one channel please: https://airbytehq-team.slack.com/archives/C01MFR03D5W/p1646280482861969