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
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
troubleshoot-missing-attrs.mdrules/
| title | impact | tags |
|---|---|---|
| Missing Attributes | MEDIUM | troubleshoot, attributes |
Missing Attributes
Impact: MEDIUM
Troubleshoot when span/resource attributes are missing.
Checklist
-
Add custom attributes - Use SDK's span API
// Node.js example span.setAttribute("user.id", userId); -
Resource attributes - Configure at SDK initialization
// Node.js example new Resource({ "deployment.environment": "production" }); -
Search by attribute - Verify attributes exist
npx @kopai/cli traces search --span-attr "key=value" --json npx @kopai/cli traces search --resource-attr "key=value" --json
Reference
https://opentelemetry.io/docs/concepts/semantic-conventions/
rules