amoghrajesh commented on code in PR #29929:
URL: https://github.com/apache/airflow/pull/29929#discussion_r1195902261
##########
airflow/config_templates/config.yml:
##########
@@ -2671,6 +2671,13 @@ kubernetes_executor:
type: string
example: '{ "total": 3, "backoff_factor": 0.5 }'
default: ""
+ detailed_executor_logs:
+ description: |
+ Flag to have more details in kubernetes executor pod logs
Review Comment:
@uranusjr thanks for the review. All the logs present under kubernetes
executor do not contain a lot of data needed to have the best debugging
experience.
Example:
When trying to trace the lifecycle of a task in the kubernetes executor, you
currently must search first for the name of the pod created by the task, then
search for the pod name in the logs. This means you need to be pretty familiar
with the structure of the scheduler logs in order to search effectively for the
lifecycle of a task that had a problem.
Some log statements like Attempting to finish pod do have the annotations
for the pod, which include dag name, task name, and run_id, but others do not.
For instance, Event: podname-a2f2c1ac706 had an event of type DELETED has no
such annotations.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
