Show running task logs in the UI with Elasticsearch remote logging#69090
Open
aeroyorch wants to merge 1 commit into
Open
Show running task logs in the UI with Elasticsearch remote logging#69090aeroyorch wants to merge 1 commit into
aeroyorch wants to merge 1 commit into
Conversation
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Running task logs were not shown in the airflow UI when using elasticsearch remote
logging, and only appeared once the task had finished. In Airflow 3 the supervisor
uploads logs to elasticsearch only after the task finishes, and the elasticsearch
handler reads only from elasticsearch, so a running task had nothing to display.
Fix:
For airflow 3, running and deferred tasks (current attempt) now delegate to the base
FileTaskHandler._read, which serves the live worker and executor logs and drivesend_of_logfrom the task state, similar to what is done by the S3/GCS backends.Was generative AI tooling used to co-author this PR?
Claude Opus 4.8 for inspecting other providers' code (GCS/S3).
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.