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
metric-filters.mdreferences/
Metric Filters Reference
Available Filters
| Filter | Flag | Example |
|---|---|---|
| Type (required) | --type | --type Gauge |
| Name | --name | --name http_requests_total |
| Service | --service | --service payment-api |
| Attributes | --attr | --attr "endpoint=/api" |
| Aggregate | --aggregate | --aggregate sum |
| Group by (attr) | --group-by | --group-by signal (repeatable) |
Metric Types
| Type | Description | Use Case |
|---|---|---|
| Gauge | Point-in-time value | Current memory, CPU, connections |
| Sum | Cumulative counter | Request counts, error counts |
| Histogram | Distribution of values | Latency percentiles |
Common Metrics
| Metric | Type | Description |
|---|---|---|
| http_requests_total | Sum | Total HTTP requests |
| http_server_errors_total | Sum | HTTP 5xx errors |
| http_server_duration | Histogram | Request latency |
| process_cpu_seconds | Sum | CPU usage |
| process_resident_memory_bytes | Gauge | Memory usage |
Output Options
| Flag | Description |
|---|---|
--json | JSON output |
--table | Table output |
--fields | Select specific fields |
--limit | Max results |
Commands
# Discover all metrics
kopai metrics discover --json
# Search specific metric
kopai metrics search --type TYPE [--name NAME] [--service NAME] --json