apache/airflow

`StackdriverTaskHandler` rework for the structlog era

已关闭

#65,191 创建于 2026年4月14日

在 GitHub 查看贡献者指南
 (0 条评论) (0 个反应) (0 位负责人)Python (16,781 个派生)batch import
area:loggingarea:providersgood first issuekind:metaprovider:google

仓库指标

星标
 (44,809 个星标)
PR 合并指标
 (平均合并 7天 18小时) (30 天内合并 834 个 PR)

描述

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.

贡献者指南

研究方向
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.
技术栈
pythongcp
领域
backendinfrastructureobservabilitycloud
议题类型
重构
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 天
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
新近可参与
清晰度议题是否清楚说明期望改动、验收标准和下一步。
清晰
前置要求
Familiarity with Airflow loggingUnderstanding of structlogKnowledge of StackDriver
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50