GitHub user dlamblin added a comment to the discussion: Info level logging from Sql Hooks stops working when commands are run from top-level code
I believe you can get some insight into what MWAA is doing in later versions of Airflow by looking at these files: - https://github.com/aws/amazon-mwaa-docker-images/blob/main/images/airflow/2.9.2/python/mwaa/logging/config.py - https://github.com/aws/amazon-mwaa-docker-images/blob/main/images/airflow/2.10.1/python/mwaa/logging/config.py - https://github.com/aws/amazon-mwaa-docker-images/blob/main/images/airflow/2.10.3/python/mwaa/logging/config.py - https://github.com/aws/amazon-mwaa-docker-images/blob/main/images/airflow/2.11.0/python/mwaa/logging/config.py - https://github.com/aws/amazon-mwaa-docker-images/blob/main/images/airflow/3.0.6/python/mwaa/logging/config.py - https://github.com/aws/amazon-mwaa-docker-images/blob/main/images/airflow/3.2.1/python/mwaa/logging/config.py There's another 3 files around each of those, and some config/env variables are pretty clearly laid out within. It doesn't cover 2.6.3 ; and I don't see it in the history, but I didn't look very hard for it. I am personally confused why my 3.0.6 setup isn't getting any logging from the standard_task_runner.py nor taskinstance.py, ending on the last message from my operator or hook without any errors from the hook, even though https://github.com/apache/airflow/blob/3.0.6/airflow-core/src/airflow/models/taskinstance.py is definitly still meant to be logging. GitHub link: https://github.com/apache/airflow/discussions/38615#discussioncomment-16903582 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
