CtrlK
BlogDocsLog inGet started
Tessl Logo

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

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

troubleshoot-wrong-port.mdrules/

titleimpacttags
Wrong PortMEDIUMtroubleshoot, port

Wrong Port

Impact: MEDIUM

Troubleshoot port confusion between collector and API.

Port Reference

PortServicePurpose
4318OTEL CollectorSend telemetry here (OTLP/HTTP)
8000API ServerQuery data here (CLI uses this)

Common Mistake

# WRONG - API server doesn't accept OTLP
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:8000

# CORRECT - Collector endpoint
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318

Verify

# Should return 200 (collector)
curl -I http://localhost:4318/v1/traces

# Should return API response
curl http://localhost:8000/signals/traces

rules

_sections.md

lang-cpp.md

lang-dotnet.md

lang-erlang.md

lang-go.md

lang-java.md

lang-nextjs.md

lang-nodejs.md

lang-php.md

lang-python.md

lang-ruby.md

lang-rust.md

setup-backend.md

setup-environment.md

troubleshoot-missing-attrs.md

troubleshoot-missing-spans.md

troubleshoot-no-data.md

troubleshoot-wrong-port.md

validate-logs.md

validate-metrics.md

validate-traces.md

SKILL.md

tile.json