[RCA] Import request-based query traces as incident evidence
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- go
- 領域
- backend, cli, observability
調査の方向性
Read the proposed bydbctl rca import-query-trace entry point, pkg/query/tracer.go, liaison query response fixtures, and the workspace artifact importer; first revalidate those seams after prerequisite #14223 merges. Add focused behavioral tests with independently documented fixtures before implementation, then record the actual RED failure and GREEN results. Done means one documented response format imports offline with provenance and privacy preserved, malformed or oversized input and output conflicts are refused, and the real CLI behavior passes its end-to-end scenarios.
索引モデルが issue の本文から書いたものです。
説明
Umbrella: #14222
Blocked by: #14223
Summary
Import request-based query traces as incident evidence. Deliver one usable operation, not a framework-only foundation.
Boundary
Proposed activation caller: bydbctl rca import-query-trace --file … --workspace …. 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. Import one explicitly documented measure-query response format containing an execution trace. Reject other formats explicitly; preserve operators, durations, node references and any reported truncation. Do not infer completeness from absent truncation metadata.
R2. Require provenance: original incident request, later armed capture, or replay. Record collection time separately from execution time; unknown execution times remain unknown.
R3. Keep query text/parameters and identifiers private; link a trace to logs only with explicit observed identity or a qualified uncertain mapping.
R4. Record that tracing may suppress slow-query logs. Missing slow logs must not be interpreted as no slow query.
Acceptance criteria
- Hand-authored original and replay responses have identical query text but different times; the output keeps separate provenance and does not merge them.
- Reject malformed and oversized input, preserve a truncated trace as partial, and demonstrate that import makes zero network calls.
- 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: pkg/query/tracer.go; liaison query response fixtures; workspace artifact importer.
- 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
Importing available query-execution evidence is required; capturing every format or replaying requests is not.
Removed/deferred: Additional response formats, automatic arming, replay, continuous tracing and retained query-trace storage.
Out of scope
Always-on query tracing, retained trace service, automatic replay, client auto-instrumentation, application trace sampling.
- 主要言語
- Java
- スター
- 25k
- フォーク
- 6.6k
- 平均マージ
- 12時間 1分
- マージ済み PR(30日)
- 43
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
apache/skywalking のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
apache/skywalking#14239 ·
メンテナーはふだん 1 日以内に返信
-
AI Assistant database enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 24/100
apache/skywalking#14237 ·
メンテナーはふだん 1 日以内に返信
-
database enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
apache/skywalking#14236 ·
メンテナーはふだん 1 日以内に返信
-
AI Assistant database enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
apache/skywalking#14235 ·
メンテナーはふだん 1 日以内に返信
-
database enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
apache/skywalking#14234 ·
メンテナーはふだん 1 日以内に返信
apache/skywalking の issue をすべて見る
似ている issue
-
account bug exercise lecture modeling programming
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
メンテナーはふだん 1 日以内に返信
-
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 日以内に返信
-
component:core regression
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
jenkinsci/jenkins#27783 · コメント 3 件 ·
メンテナーはふだん 2 日以内に返信