kopai/root-cause-analysis
Analyze telemetry data for root cause analysis using Kopai CLI. Use when debugging errors, investigating latency issues, tracing request flows across services, or correlating logs with traces. Also use when users report production issues like "why is my API slow", "getting 500 errors", "service is down", "requests are timing out", or any symptom that needs telemetry-based investigation — even if they don't mention traces or observability explicitly.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
workflow-get-context.mdrules/
| title | impact | tags |
|---|---|---|
| Step 2: Get Full Trace Context | CRITICAL | workflow, trace, context, step2 |
Step 2: Get Full Trace Context
Impact: CRITICAL
Get complete trace details with all spans.
Get Trace
npx @kopai/cli traces get <traceId> --jsonAnalysis Points
| Field | What to Look For |
|---|---|
| ParentSpanId | Span hierarchy/call chain |
| Duration | Slow spans (bottlenecks) |
| SpanAttributes | Request context, parameters |
| StatusMessage | Error details, exception info |
| StatusCode | OK or ERROR |
Select Specific Fields
npx @kopai/cli traces get <traceId> --fields SpanName,Duration,StatusCode --jsonReference
See references/trace-filters.md for output options