Otel Agent Trace Connector — Development skill for Claude Code
OpenTelemetry Collector connector for normalized Codex and Claude Code traces.
How to install Otel Agent Trace Connector
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open nijave/otel-agent-trace-connector and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Otel Agent Trace Connector does
OpenTelemetry Collector connector for normalized Codex and Claude Code traces.
Alternatives in Development
- Hivemind — Hivemind turns your traces into reusable skills across agents 1.6k ★
- Opik Openclaw — 🦞 Official plugin for OpenClaw that exports agent traces to Opik 725 ★
- Claude Code Otel — A comprehensive observability solution for monitoring Claude Code usage, performance, and costs 306 ★
README
Coding-agent OpenTelemetry connector
An organization adopting AI coding agents receives telemetry in as many shapes as it runs agents. This connector normalizes those shapes into one canonical trace vocabulary so the same queries measure token usage — and the cost derived from it — across every agent. Latency and tool activity ride the same spans. Prompt text, tool arguments, and tool output never enter canonical output, so usage visibility does not require collecting what developers type. [docs/design.md](docs/design.md) records the use case and design goals.
This repository provides an external OpenTelemetry Collector connector and an OCB-built distribution for coding-agent traces:
- Codex: correlates structured
codex.*OTLP logs into one canonical trace per user turn. - Cursor: correlates native
cursor.telemetryOTLP logs (Enterprise beta, metrics + logs only) into one canonical trace per activity burst, keyed oncursor.conversation.id. Chat spans carry per-request token usage; the wire reports tool calls only as metrics without correlation IDs, so canonical traces have noexecute_toolchildren. - OpenCode: renames its native Vercel AI SDK spans (
ai.streamText,ai.streamText.doStream,ai.toolCall) into oneinvoke_agent opencodecanonical trace per model step, dropping internal instrumentation spans and all content attributes. - GitHub Copilot: normalizes native GenAI-semconv traces from Copilot CLI
and VS Code Chat (
invoke_agent/chat/execute_tool) through the shared GenAI-semconv edge - Claude Code: preserves its native span hierarchy and normalizes the interaction, LLM, and tool span names and attributes into the same canonical vocabulary.
- GenAI semconv sources: normalizes native traces from
opentelemetry-instrumentation-openai-v2(both semconv modes), directopentelemetry-util-genaiusers, and the Strands Agents SDK into the same canonical vocabulary, stripping prompt/complet
Related Skills
Otel Collector
Generate an otelcol-contrib config (agent or gateway mode)
Trace Insight
Read-only report from local Claude, Codex, and Pi agent traces
Docs Observability
Open ArchiPy OpenTelemetry guidance (traces, metrics, logs)
Scaffold Observability
Configure ArchiPy 5.x OpenTelemetry traces, metrics, logs, and instrumentation
Diagnose Deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
Lmcache Agent Trace
Agent application/benchmark/workload traces should be placed here.
Related Agents
Otel Trace
Investigate OpenTelemetry traces in Berserk — span analysis, latency debugging, trace correlation, service dep
Otel Observability Engineer
Independent observability reviewer for a service diff — verifies OpenTelemetry instrumentation, RED metrics (R
Instrumentation Gen
Generates language-specific OpenTelemetry SDK bootstrap files (Node.js / Python) from the context cache. Dispa