[
https://issues.apache.org/jira/browse/AIRFLOW-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714862#comment-16714862
]
ASF GitHub Bot commented on AIRFLOW-3492:
-----------------------------------------
ashb closed pull request #4301: [AIRFLOW-3492] Addition of Unique ID required
in every Airflow Task Log for debugging purpose
URL: https://github.com/apache/incubator-airflow/pull/4301
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/airflow/config_templates/airflow_local_settings.py
b/airflow/config_templates/airflow_local_settings.py
index 45a2f2923c..ba257d51f6 100644
--- a/airflow/config_templates/airflow_local_settings.py
+++ b/airflow/config_templates/airflow_local_settings.py
@@ -21,6 +21,7 @@
from airflow import configuration as conf
from airflow.utils.file import mkdirs
+import uuid
# TODO: Logging format and level should be configured
# in this file instead of from airflow.cfg. Currently
@@ -64,7 +65,7 @@
'disable_existing_loggers': False,
'formatters': {
'airflow': {
- 'format': LOG_FORMAT,
+ 'format': LOG_FORMAT + ' [' + str(uuid.uuid1()) + ']',
},
},
'handlers': {
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
