You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/05/14 09:25:56 UTC

[GitHub] [airflow] ewjmulder edited a comment on issue #8484: Airflow 1.10.7+ suppresses Operator logs

ewjmulder edited a comment on issue #8484:
URL: https://github.com/apache/airflow/issues/8484#issuecomment-628512253


   We experienced a similar issue after upgrading from 1.10.3 to 1.10.9: no more task logging visible in the UI. In our case it was specifically for the KubernetesPodOperator, but not for the BashOperator for instance. We fixed it by adding a logger for the airflow.contrib package (in the main airflow logging configuration file, see snippet below), since the KubernetesPodOperator lives there. So if the operator you're missing logs from is also from the contrib package, you can try this fix to see if it re-appears. Probably it also works for other operators, as long as you specify the right package they are in as extra logger.
   
   My guess is that the combination of forking instead of starting a whole new process + having no specific logger for the package triggered this particular issue. Hope it solves it for you too.
   
   Added log config snippet:
   ```
           'airflow.contrib': {
               'handlers': bucket_handler,
               'level': LOG_LEVEL,
               'propagate': True,
           }
   
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org