[RCA] Record component versions and incident-local identity mapping

Aperta
#14,224 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go
Ambito
observability

Direzione di ricerca

Read prerequisite issue #14223 and inspect the workspace manifest it introduces, then trace the existing FODC identity fields and pkg/version. The proposed entry point is bydbctl rca inventory; its command and package seams are not established yet. Done means the command preserves mixed and unknown versions, records explicit mappings, refuses ambiguous joins and output conflicts, and passes focused TestRCA behavioral tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

database enhancement

Umbrella: #14222

Blocked by: #14223

Summary

Record component versions and incident-local identity mapping. Deliver one usable operation, not a framework-only foundation.

Boundary

Proposed activation caller: bydbctl rca inventory --workspace … --input inventory.json. 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. Ingest an explicit reporter-supplied component inventory; record role, original node/pod reference, version, commit and image digest with source and observation time. No Kubernetes credentials or automatic cluster-wide discovery are required for this first slice.
R2. Preserve mixed versions, conflicts and unknown values. Never infer every node version from the collector or a single pod.
R3. Assign stable workspace-local component references; store explicit mappings between observed native-log/FODC identities. Ambiguous mappings remain unresolved; do not silently join equal display names.
R4. Record collector/build/schema versions independently of database versions. Keep raw names and mapping material private for later release transformation.

Acceptance criteria

  • A manually authored inventory contains data nodes on versions A and B, an unknown FODC build, and duplicate pod names in different namespaces. Output preserves both builds and refuses the ambiguous join.
  • Run inventory against the workspace from #14223; verify every declared reference resolves or has an explicit unresolved reason, and inventory ingestion changes no original evidence.
  • 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/version; existing FODC identity fields; workspace manifest introduced by #14223.
  • 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 under bydbctl/internal/cmd and/or the introduced collector package;
    run go test ./bydbctl/internal/cmd -run TestRCA -count=1 plus 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

Per-component provenance and explicit identity mapping are required; automatic discovery is not.

Removed/deferred: Automatic Kubernetes discovery, image-tag inference, heuristic identity matching and producer-wide naming changes.

Out of scope

Changing every telemetry producer, guessing versions from image tags, Kubernetes discovery, universal naming migration.

Lingua principale
Java
Stelle
25k
Fork
6.6k
Merge medio
12h 1m
PR unite (30g)
43

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/skywalking

Tutte le issue di apache/skywalking

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.