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-check-metrics.mdrules/
| title | impact | tags |
|---|---|---|
| Step 4: Check Metrics | CRITICAL | workflow, metrics, step4 |
Step 4: Check Metrics
Impact: CRITICAL
Examine metrics to understand system state during the issue.
Discover Available Metrics
npx @kopai/cli metrics discover --jsonCheck Error Rate Metrics
npx @kopai/cli metrics search --type Sum --name http_server_errors_total --jsonCheck Latency Metrics
npx @kopai/cli metrics search --type Histogram --name http_server_duration --jsonFilter by Service
npx @kopai/cli metrics search --type Gauge --service payment-api --jsonReference
See references/metric-filters.md for all filter options