[RCA] Import request-based query traces as incident evidence
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- backend, cli, observability
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Java
- Estrellas
- 25k
- Forks
- 6.6k
- Merge medio
- 12 h 1 min
- PR fusionados (30 d)
- 43
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/skywalking
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/skywalking#14239 ·
Los mantenedores suelen responder en 1 día
-
AI Assistant database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 24/100
apache/skywalking#14237 ·
Los mantenedores suelen responder en 1 día
-
database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
apache/skywalking#14236 ·
Los mantenedores suelen responder en 1 día
-
AI Assistant database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
apache/skywalking#14235 ·
Los mantenedores suelen responder en 1 día
-
database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
apache/skywalking#14234 ·
Los mantenedores suelen responder en 1 día
Todos los issues de apache/skywalking
Issues similares
-
account bug exercise lecture modeling programming
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Posiblemente ocupada @dbusche la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
h2database/h2database#4580 ·
Los mantenedores suelen responder en 1 día
-
vips-drift
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Stirling-Tools/JPDFium#300 ·
Los mantenedores suelen responder en 1 día
-
hermes-queue
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Los mantenedores suelen responder en 1 día
-
component:core regression
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
jenkinsci/jenkins#27783 · 3 comentarios ·
Los mantenedores suelen responder en 2 días