[GitHub] guptakumartanuj opened a new pull request #4301: [AIRFLOW-3492] Addition of Unique ID required in every Airflow Task Log for debugging purpose

[GitBox <gi...@apache.org>]

guptakumartanuj opened a new 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
 
 
   Currently we are using Airflow as our main orchestrator and in turn we need all the Airflow logs at one place. In the current system, 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. 
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow-3492](https://issues.apache.org/jira/browse/AIRFLOW-3492) issues and references them in the PR title. 
     - https://issues.apache.org/jira/browse/AIRFLOW-3492
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
   
   ### Code Quality
   
   - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services