Remove per-invocation Lambda lifecycle INFO logs
维护者通常 2 天内回复
还没有人认领这个 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
- 平均合并
- 3 天 7 小时
- 30 天内合并 PR
- 11
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AbsaOSS/EventGate 的其他 Issue
-
refactoring type:tech-debt
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 2 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 2 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 32/100
维护者通常 2 天内回复
-
infrastructure type:tech-debt
难度 3/5 1-2 天 新手友好度 70/100
维护者通常 2 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 70/100
维护者通常 2 天内回复
查看 AbsaOSS/EventGate 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
area:docs
难度 2/5 1-3 小时 新手友好度 72/100
RailtownAI/railtracks#1633 ·
维护者通常 2 天内回复
-
review-panel severity:low
难度 1/5 1 小时以内 新手友好度 85/100
kristovatlas/coin-accounting#152 ·
维护者通常 1 天内回复
-
documentation :blue_book:
难度 1/5 1 小时以内 新手友好度 88/100
PennyLaneAI/pennylane#10280 ·
维护者通常 2 天内回复
-
`pipx reinstall` prints a Python traceback when the reinstall fails可能已有人在做 @ParamTanna 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复