Fix: Restore live stdout logging for Elasticsearch in Airflow 3#64067
Open
Subham-KRLX wants to merge 1 commit intoapache:mainfrom
Open
Fix: Restore live stdout logging for Elasticsearch in Airflow 3#64067Subham-KRLX wants to merge 1 commit intoapache:mainfrom
Subham-KRLX wants to merge 1 commit intoapache:mainfrom
Conversation
Contributor
1 task
Contributor
|
cc @Owen-CH-Leung for review as the expert :) |
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.
This PR restores the ElasticsearchTaskHandler in DEFAULT_LOGGING_CONFIG within airflow_local_settings.py, resolving the regression where task logs were no longer visible in stdout after upgrading to Airflow 3.While ElasticsearchRemoteLogIO
was previously added for remote retrieval, the handler itself was omitted from the configuration block. This caused Airflow to fall back to the generic FileTaskHandler, which does not support the write_stdout configuration. Restoring the handler ensures that logs are correctly sent to stdout(for Fluentd/container log shippers) when configured.
This aligns the Elasticsearch provider's logging configuration with the patterns used by Opensearch and Stackdriver.
closes: #63960
closes: #49863
closes: #54501
Was generative AI tooling used to co-author this PR?
Yes — Gemini (Code Research and PR Description)