Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Investigate and clarify logging [was: DAG logs are not persisted]

未關閉
#416 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@razvan 已經在處理了。

開始於 2024年4月5日。

評估

這個 Issue 還沒有評估資料。

描述

type/bug

Update April 5th: @razvan hijacked this issue to add more clarifications to how logging works in Airflow in various circumstances. The documentation regarding logging is quite bare.

While investigating a CVE a couple of questions popped out that need clarification.

  • How/Where are logs written by the different roles/groups ?
  • How is the /stackable/airflow/log folder handled by the different roles (scheduler, executor, webserver) ? Why does it even contain files if we configure Airflow to write everything to /stackable/logs ?
  • How do the permissions of /stackable/logs come to be ? This folder is created multiple places:
    • the Pod command
    • log_config.py
  • ...

Following is the original request of this issue
DAG logs are ephemeral. When using the Kubernetes executor, they are only available on the executor pods and are lost when the pods are destroyed. This can be mitigated by the vector log collection infrastructure to save the logs to a remote system. The problem remains that the logs are not accessible via Airflow's web UI.

In addition, during tests it was found that the logs are not accessible in the Airflow web ui even while the executor pods are still alive. This is the bug aspect of this ticket that requires some more investigation.

主要語言
Rust
星號
32
分支
6
平均合併
21 小時 38 分鐘
30 天內合併 PR
13

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

stackabletech/airflow-operator 的其他 Issue

查看 stackabletech/airflow-operator 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。