[
https://issues.apache.org/jira/browse/AIRFLOW-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ash Berlin-Taylor resolved AIRFLOW-3492.
----------------------------------------
Resolution: Won't Fix
Airflow supports running with a custom logging config (`logging_config_class`
in airflow.cfg) - if you want this feature that is where this should go.
> Addition of Unique ID required in every Airflow Task Log for debugging purpose
> ------------------------------------------------------------------------------
>
> Key: AIRFLOW-3492
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3492
> Project: Apache Airflow
> Issue Type: Improvement
> Components: logging
> Reporter: Tanuj Gupta
> Assignee: Tanuj Gupta
> Priority: Minor
>
> Use Case: Currently we are using Airflow as our main orchestrator and all of
> task logs of a particular DAG are forwarded to Splunk. Due to security
> reason, Airflow UI is not accessible to all the clients. So, we don't have
> any way to co-relate all the logs of a particular task in a DAG while
> searching in Splunk.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
