[RCA] Collect bounded FODC metric windows
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
调研方向
Start by resolving the blocked prerequisite #14223, then inspect the FODC API handlers in fodc/proxy/internal/api/server.go for /metrics-windows and /metrics, along with the existing metric-window tests. The CLI entry point and final test paths depend on seams introduced by that prerequisite. Done means a usable bounded collection operation, honest coverage and source status, and the specified fixture, timeout, malformed-response, oversized-response, cancellation, and conflict tests pass.
由索引模型根据 Issue 内容生成。
描述
Umbrella: #14222
Blocked by: #14223
Summary
Collect bounded FODC metric windows. Deliver one usable operation, not a framework-only foundation.
Boundary
Proposed activation caller: bydbctl rca collect --source=fodc-metrics. Command names are proposed, not existing APIs.
Reporter collection runs with read-only source access; offline steps use local files only.
No source storage/wire-format changes are requested. The incident format is separately versioned.
Requirements
R1. Collect the requested incident window through the existing FODC API with explicit endpoint, node filters, deadline and byte cap.
R2. Preserve metric names, labels, timestamps and source identity; record requested versus observed time ranges and missing agents where the API provides them.
R3. Distinguish partial, unavailable, empty and complete evidence. Do not claim the recorder retained data outside its reported window; if coverage cannot be proved, record unknown.
R4. Write into the same private manifest without overwriting the native-log source status. Propagate cancellation and cap retries.
Acceptance criteria
- A recorded API fixture has two agents, one expired interval and one unavailable agent. Independently specified samples survive unchanged and coverage names both gaps.
- Exercise the CLI against a FODC fixture server including timeout, malformed response and an oversized response. All terminate within configured test bounds and leave an honest source status.
- Use hand-authored or independently captured fixtures with documented provenance; do not generate expected values using the code under test.
- Add focused behavioral tests before implementation and record the actual RED command/failure, then GREEN results.
- Keep existing CLI/API behavior compatible. Never overwrite unrelated user files; output conflicts must be refused.
Scope and readiness audit
- Boundary and behavior: the single operation above; independently observable output and refusal behavior.
- Production activation: the named CLI or skill entry point above, included in the same PR.
- Packages/callers: fodc/proxy/internal/api/server.go /metrics-windows and /metrics; existing FODC metric-window tests.
- Dependencies: #14223
- Classification: planned blocked leaf; revalidate prerequisite seams after merge.
- RED evidence: not executed during this planning task; no claim of passing or failing implementation tests.
- End-to-end proof: the real command/skill scenarios above, not source-text assertions.
- Formats/lifecycle/fixtures: private workspace or public archive only; artifact-specific fixture family above.
- Focused tests: CLI leaves should add
TestRCA…coverage underbydbctl/internal/cmdand/or the introduced collector package;
rungo test ./bydbctl/internal/cmd -run TestRCA -count=1plus the new package tests. Skill leaves must add a replayable evaluation harness
with an exact command documented in the PR. Final test names/paths are fixed when the prerequisite seam merges. - Resource/concurrency checks: cancellation, bounded reads/output and cleanup on failure; use repository panic-aware goroutine wrappers if concurrency is introduced.
- Decision: one proposed PR. If the named behavior requires an unimplemented server API or another lifecycle change, stop and split that prerequisite.
Required-only scope audit
Metrics are a requested diagnostic source; a new monitoring system is not.
Removed/deferred: New metric retention, new alert configuration, automatic discovery and new collection endpoints.
Out of scope
New metric retention, Prometheus deployment, alerts, changing FODC ring buffers.
- 主要语言
- Java
- 星标
- 25k
- 派生
- 6.6k
- 平均合并
- 12 小时 1 分钟
- 30 天内合并 PR
- 43
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
apache/skywalking 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
apache/skywalking#14239 ·
维护者通常 1 天内回复
-
AI Assistant database enhancement
难度 5/5 一周以上 新手友好度 24/100
apache/skywalking#14237 ·
维护者通常 1 天内回复
-
database enhancement
难度 5/5 一周以上 新手友好度 25/100
apache/skywalking#14236 ·
维护者通常 1 天内回复
-
AI Assistant database enhancement
难度 5/5 一周以上 新手友好度 25/100
apache/skywalking#14235 ·
维护者通常 1 天内回复
-
database enhancement
难度 5/5 一周以上 新手友好度 30/100
apache/skywalking#14234 ·
维护者通常 1 天内回复
查看 apache/skywalking 的全部 Issue
相似的 Issue
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)可能已有人在做 @dbusche 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
h2database/h2database#4580 ·
维护者通常 1 天内回复
-
vips-drift
难度 2/5 1-3 小时 新手友好度 74/100
Stirling-Tools/JPDFium#300 ·
维护者通常 1 天内回复
-
hermes-queue
难度 1/5 1-3 小时 新手友好度 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
维护者通常 1 天内回复
-
Guidelines: document how to build a use case against a local, unpublished Flow/browserless-test change可能已有人在做 @totally-not-ai 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 88/100
vaadin/use-cases#452 · 1 条评论 ·
维护者通常 1 天内回复
-
area/storage area/storage/sql
难度 2/5 1-3 小时 新手友好度 78/100
Apicurio/apicurio-registry#11159 ·
维护者通常 1 天内回复