Remove per-invocation Lambda lifecycle INFO logs
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 64/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- aws, python
研究方向
Locate the EventGate and EventStats Lambda entry points and the code emitting lifecycle messages, then review ADR-002 and the existing request-completion logging. Exercise both warm and normal invocations with LOG_LEVEL=INFO and add or run tests that count INFO records. Done means each invocation has one structured Request completed. record, with step detail remaining at DEBUG.
由索引模型根據 Issue 內容生成。
描述
Describe the bug
Lambda invocations emit additional plaintext lifecycle messages such as lambda started and lambda finished alongside request logs. This violates ADR-002 observability logging budget: one INFO request-outcome record per invocation, with outcome data attached as structured fields rather than additional lines.
Steps to Reproduce
- Invoke either EventGate or EventStats Lambda with
LOG_LEVEL=INFO. - Inspect CloudWatch logs for one invocation.
- Observe plaintext Lambda start/finish lifecycle messages in addition to structured request completion output.
Expected state
For each normal Lambda invocation, emit exactly one request-scoped INFO record: Request completed.
- Include status, duration, correlation ID, and handler outcome as structured JSON fields.
- Keep request step detail at
DEBUG. - Preserve ADR-approved container-lifecycle records only when tied to cold start, initialization, or connection age.
- Remove or downgrade per-invocation plaintext lifecycle messages so they cannot inflate INFO log volume.
Impact / Severity
Low
Attachments / Evidence
ADR-002, “Logging strategy”:
- One
INFOline per request. - Handler outcomes must use fields on completion record, not extra log lines.
- Lifecycle INFO records allowed only when tied to container or connection age, not request count.
Verify both EventGate and EventStats Lambda paths, including warm invocations, using tests that assert INFO-record count per invocation.
- 主要語言
- Python
- 星號
- 4
- 分支
- 0
- 平均合併
- 10 小時 56 分鐘
- 30 天內合併 PR
- 6
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
AbsaOSS/EventGate 的其他 Issue
-
refactoring type:tech-debt
難度 2/5 1-3 小時 新手友好度 84/100
-
enhancement
難度 2/5 1-3 小時 新手友好度 70/100
-
enhancement
難度 4/5 3-5 天 新手友好度 56/100
-
enhancement
難度 5/5 一週以上 新手友好度 32/100
-
infrastructure type:tech-debt
難度 3/5 1-2 天 新手友好度 70/100
查看 AbsaOSS/EventGate 的全部 Issue
相似的 Issue
-
Import errors are swallowed: PerthImplicitWatermarker silently becomes None可能已有人在做 @JonRC 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
resemble-ai/Perth#23 ·
-
correction metadata
難度 2/5 1 小時以內 新手友好度 65/100
acl-org/acl-anthology#10753 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
earthtojake/text-to-cad#758 ·
維護者通常 1 天內回覆
-
難度 1/5 1-3 小時 新手友好度 70/100
DataTalksClub/faq#545 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆