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