[RCA] Sanitize query-execution traces
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
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
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di apache/skywalking
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/skywalking#14239 ·
I maintainer di solito rispondono entro 1 giorno
-
AI Assistant database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 24/100
apache/skywalking#14237 ·
I maintainer di solito rispondono entro 1 giorno
-
database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
apache/skywalking#14236 ·
I maintainer di solito rispondono entro 1 giorno
-
AI Assistant database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
apache/skywalking#14235 ·
I maintainer di solito rispondono entro 1 giorno
-
database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
apache/skywalking#14234 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di apache/skywalking
Issue simili
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Forse già presa @dbusche l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
h2database/h2database#4580 ·
I maintainer di solito rispondono entro 1 giorno
-
vips-drift
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
Stirling-Tools/JPDFium#300 ·
I maintainer di solito rispondono entro 1 giorno
-
hermes-queue
Difficoltà 1/5 1-3 ore Idoneità per principianti 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
I maintainer di solito rispondono entro 1 giorno
-
Guidelines: document how to build a use case against a local, unpublished Flow/browserless-test changeForse già presa @totally-not-ai l’ha presa oggi. Aperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
vaadin/use-cases#452 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
area/storage area/storage/sql
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Apicurio/apicurio-registry#11159 ·
I maintainer di solito rispondono entro 1 giorno