kopai/otel-instrumentation

Instrument applications with OpenTelemetry SDK and validate telemetry using Kopai. Use when setting up observability, adding tracing/logging/metrics, testing instrumentation, debugging missing telemetry data, or when traces/logs/metrics aren't appearing after setup. Also use when users say things like "my traces aren't showing up", "I don't see any data", or "how do I add observability to my app".

100

Quality

100%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Kopai CLI Reference

Name: kopai/otel-instrumentation
Rating: 1 (1 reviews)
Author: kopai

Note: Use npx @kopai/cli or kopai (if globally installed)

Traces

# Search traces
kopai traces search [--service NAME] [--span-name NAME] [--status-code OK|ERROR] [--json]

# Get specific trace
kopai traces get <traceId> [--json]

# Advanced filters
kopai traces search --span-attr "key=value" --json
kopai traces search --resource-attr "key=value" --json
kopai traces search --duration-min 1000000000 --json  # 1s in ns

Logs

# Search logs
kopai logs search [--service NAME] [--severity-text ERROR] [--body TEXT] [--json]

# Correlate with trace
kopai logs search --trace-id <traceId> --json

# Filter by attributes
kopai logs search --log-attr "key=value" --json

Metrics

# Discover metrics
kopai metrics discover [--json]

# Search metrics (type required)
kopai metrics search --type TYPE [--name NAME] [--json]

# Aggregate: total sum, no grouping
kopai metrics search --type Sum --name kopai.ingestion.bytes --aggregate sum --json

# Aggregate: sum grouped by attribute key
kopai metrics search --type Sum --name kopai.ingestion.bytes --aggregate sum --group-by signal --json

Output Options

Flag	Description
--json	JSON output (pipe to jq)
--table	Table output
--fields F1,F2	Select fields
--limit N	Max results

Full Documentation

https://github.com/kopai-app/kopai-mono/tree/main/packages/cli