`StackdriverTaskHandler` rework for the structlog era · apache/airflow#65191

(0 评论) (0 反应) (0 负责人)Python (44,809 star) (16,781 fork)batch import

area:loggingarea:providersgood first issuekind:metaprovider:google

描述

Body

Following https://github.com/apache/airflow/pull/48491

Reference: https://github.com/apache/airflow/pull/48788

In Airflow 3, the task execution path was rearchitected: task workers now use structlog and communicate with a RemoteLogIO (set as REMOTE_TASK_LOGin the logging config module) rather than through a Python stdlib logging. Handler registered inDEFAULT_LOGGING_CONFIG`.

All major remote log backends have been migrated to this new pattern — S3, GCS, CloudWatch, WASB, OSS, HDFS (recently in #48788), and Elasticsearch. Similar effort is needed for StackDriver

Committer

I acknowledge that I am a maintainer/committer of the Apache Airflow project.

贡献者指南

技术栈: pythongcp
领域: backendinfrastructureobservabilitycloud
议题类型: refactor
难度: 3
预计时间: 1-2 days
活动状态: fresh
清晰度: clear
前置要求: Familiarity with Airflow loggingUnderstanding of structlogKnowledge of StackDriver
新手友好度: 50
研究方向: Examine the referenced PRs (#48491, #48788) to understand the pattern used for migrating remote log backends to structlog. Implement the same changes for the StackDriverTaskHandler, likely located in airflow/providers/google/cloud/logging/stackdriver task handler.py. Ensure the handler uses the RemoteLogIO interface and structlog instead of the stdlib logging handler. Follow the structure of similar migrated handlers such as S3 or GCS.