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
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
| title | impact | tags |
|---|---|---|
| Sections | CRITICAL | index, sections |
Impact: CRITICAL
Section definitions for root cause analysis rules.
| Section | Impact | Files |
|---|---|---|
| workflow | CRITICAL | workflow-find-errors.md, workflow-get-context.md, workflow-correlate-logs.md, workflow-check-metrics.md, workflow-identify-cause.md |
| pattern | HIGH | pattern-http-errors.md, pattern-slow-requests.md, pattern-distributed.md, pattern-log-driven.md |