[RCA] Sanitize query-execution traces

Aperta
#14,233 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli, observability

Direzione di ricerca

Wait for #14228 and #14230 to merge and fix the response format and policy contracts before starting. Then inspect the existing bydbctl rca sanitize command, its sanitizer caller, and the selected collector’s format; add an independent trace fixture and test through the merged CLI seam. Done means the CLI preserves approved edges, durations, provenance, and aliases, excludes unsafe content with review reasons, and keeps partial coverage partial.

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

Descrizione

database enhancement query tracing

Umbrella: #14222

Blocked by: #14228, #14230

Summary

Query traces imported by #14228 need public-safe operator evidence.

Boundary

Activation: bydbctl rca sanitize --selection … --policy …. Extend the same CLI and policy contract, not a new service.
Commands are proposed, not implemented. No database storage/wire-format changes.

Requirements

R1. Support only the response format explicitly selected in #14228 through the existing sanitizer caller.
R2. Retain approved operator relationships, durations and timing; remove query text, literals and arbitrary operator-detail strings unless a typed rule permits them.
R3. Alias approved resource/node identifiers with the shared incident mapping; retain original-versus-replay provenance.
R4. Preserve partial/unknown coverage. Unknown fields/formats fail closed or are excluded with review reasons.

Acceptance criteria

  • An independent trace fixture retains exact approved operator edges/durations, no literal canaries and the expected node alias.
  • Original and replay traces remain distinct; a partial trace never becomes complete after sanitization.
  • Invoke the actual sanitizer CLI; maintain independent golden fixtures, not expected values produced by the implementation under test.
  • Bound input/output sizes and leave raw evidence unchanged on success and failure. Unknown artifact types never bypass policy.
  • Add a test-only patch using a merged CLI seam that fails by assertion on the base, then passes with the implementation.

Scope and readiness audit

  • Classification: planned blocked leaf; not ready for GraphLoom until prerequisites merge and exact format/policy contracts are fixed.
  • Dependencies: #14228, #14230
  • Boundary and production activation: one typed transformation via the existing sanitizer command.
  • Scope: bydbctl RCA sanitization package and command; one independent format fixture family.
  • RED evidence: not executed in this drafting task. Plan a named TestRCA test through an existing command seam, not an import of new production APIs.
  • Focused tests: run the selected Go regression and changed-package tests after generation; exact selector must be fixed before queueing.
  • End-to-end proof: selected private artifact to expected candidate derivative plus exclusion report.
  • Compatibility/lifecycle: existing supported artifacts remain valid; preserve cancellation, size bounds, output isolation and alias consistency.
  • Decision: one proposed PR after the merged seam is revalidated; no model needed for safety decisions.

Required-only scope audit

Query traces imported by #14228 need public-safe operator evidence. Format support is deliberately limited to the corresponding collector. No generalized arbitrary-content sanitization.

Out of scope

Raw pprof/core/database file release, automatic publication, AI-only sanitization, generic secret-detection guarantees and new telemetry capture.

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.