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-correlate-logs.mdrules/
| title | impact | tags |
|---|---|---|
| Step 3: Correlate Logs | CRITICAL | workflow, logs, correlation, step3 |
Step 3: Correlate Logs with Trace
Impact: CRITICAL
Find logs associated with a trace for additional context.
Get All Logs for Trace
npx @kopai/cli logs search --trace-id <traceId> --jsonFilter by Severity
npx @kopai/cli logs search --trace-id <traceId> --severity-text ERROR --jsonSearch Log Body
npx @kopai/cli logs search --trace-id <traceId> --body "exception" --jsonMultiple Filters
npx @kopai/cli logs search --trace-id <traceId> --severity-text ERROR --body "timeout" --jsonReference
See references/log-filters.md for all filter options