[jira] [Commented] (AIRFLOW-7065) Give StreamLogHandler ability to tee to log and console

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138760#comment-17138760 ] 

ASF GitHub Bot commented on AIRFLOW-7065:
-----------------------------------------

stale[bot] commented on pull request #7740:
URL: https://github.com/apache/airflow/pull/7740#issuecomment-645586019


   This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
   


----------------------------------------------------------------
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


> Give StreamLogHandler ability to tee to log and console
> -------------------------------------------------------
>
>                 Key: AIRFLOW-7065
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-7065
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: logging
>    Affects Versions: 1.10.9
>            Reporter: Christopher
>            Assignee: Christopher
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> It would be helpful in some use case (ie log aggregation) to have Airflow task output stream to console as well as go through the Airflow logger. Currently stdout and stderr are captured and sent only to the logger - putting a StreamLogHandler in the logging chain results in an infinite recursion.
> I propose adding a configuration flag [core][task_console_output] that would allow safe display of messages in the console as well as propagation to the Airflow logging chain.
> I will put in a PR for this shortly and see how it goes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)