fix(observability): pin one telemetry snapshot per Logs and Trace response
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
调研方向
Start by locating the Logs and Trace response entry points and the existing telemetry statement/index, cache-acknowledgement, and contribution reads. Add deterministic tests that publish, compact, or retain telemetry between response stages, then verify one file set across entries, counts, and trace/log sections; also check cancellation cleanup, publisher progress, and the native and race suites.
由索引模型根据 Issue 内容生成。
描述
The whole-PR review of #272 identified a low-severity, pre-existing response consistency gap outside its five inline findings: https://github.com/labstack/fanout/pull/272#pullrequestreview-5386440469 .
Logs queries entries and histogram separately. Trace queries a candidate, reads its index, and fetches related logs in separate snapshots. A telemetry publication between those operations can make sections of the same response describe different active file sets.
Pin one bounded telemetry snapshot for every statement/index read that contributes to a single Logs or Trace response. Read cache acknowledgements and contributions transactionally under that snapshot; preserve immediately visible uncached files, exact clipped windows, redaction, cancellation and publisher progress. Define transaction/lock ownership once rather than adding retries or snapshot fallbacks.
Acceptance: deterministic tests publish, compact or retain telemetry between response stages and prove entries/counts and trace/log sections describe one file set. Cancellation releases all resources; publishers still progress under the existing reader grace period; the full native and race suites pass.
- 主要语言
- Go
- 星标
- 6
- 派生
- 0
- 平均合并
- 2 小时 25 分钟
- 30 天内合并 PR
- 25
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
labstack/fanout 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 42/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
相似的 Issue
-
Named Tuple element with a space in its name fails to parse可能已有人在做 @spicysharkco 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
ClickHouse/clickhouse-go#2073 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
ci: nothing regenerates the Go contract types, so a hand-edit to types.gen.go passes可能已有人在做 @shaiknoorullah 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
shaiknoorullah/hg-mono#993 · 2 条评论 ·
维护者通常 1 天内回复
-
type:bug
难度 2/5 1-3 小时 新手友好度 72/100
CarlosDanielDev/aiacc#78 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100