GitHub - DEVtheOPS/opencode-plugin-otel: An opencode plugin that exports telemetry via OpenTelemetry (OTLP/gRPC), mirroring the same signals as Claude Code's monitoring.

An opencode plugin that exports telemetry via OpenTelemetry (OTLP/gRPC), mirroring the same signals as Claude Code's monitoring.

What it instruments

Metrics

Metric	Type	Description
`opencode.session.count`	Counter	Incremented on each `session.created` event
`opencode.token.usage`	Counter	Per token type: `input`, `output`, `reasoning`, `cacheRead`, `cacheCreation`
`opencode.cost.usage`	Counter	USD cost per completed assistant message
`opencode.lines_of_code.count`	Counter	Lines added/removed per `session.diff` event
`opencode.commit.count`	Counter	Git commits detected via bash tool
`opencode.tool.duration`	Histogram	Tool execution time in milliseconds
`opencode.cache.count`	Counter	Cache activity per message: `type=cacheRead` or `type=cacheCreation`
`opencode.session.duration`	Histogram	Session duration from created to idle in milliseconds
`opencode.message.count`	Counter	Completed assistant messages per session
`opencode.session.token.total`	Histogram	Total tokens consumed per session, recorded on idle
`opencode.session.cost.total`	Histogram	Total cost per session in USD, recorded on idle
`opencode.model.usage`	Counter	Messages per model and provider
`opencode.retry.count`	Counter	API retries observed via `session.status` events

Log events

Event	Description
`session.created`	Session started
`session.idle`	Session went idle (includes total tokens, cost, messages)
`session.error`	Session error
`user_prompt`	User sent a message (includes `prompt_length`, `model`, `agent`)
`api_request`	Completed assistant message (tokens, cost, duration)
`api_error`	Failed assistant message (error summary, duration)
`tool_result`	Tool completed or errored (duration, success, output size)
`tool_decision`	Permission prompt answered (accept/reject)
`commit`	Git commit detected

Installation

Add the plugin to your opencode config at ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@devtheops/opencode-plugin-otel"]
}

Or point directly at a local checkout for development:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["/path/to/opencode-plugin-otel/src/index.ts"]
}

Configuration

All configuration is via environment variables. Set them in your shell profile (~/.zshrc, ~/.bashrc, etc.).

Variable	Default	Description
`OPENCODE_ENABLE_TELEMETRY`	(unset)	Set to any non-empty value to enable the plugin
`OPENCODE_OTLP_ENDPOINT`	`http://localhost:4317`	gRPC OTLP collector endpoint
`OPENCODE_OTLP_METRICS_INTERVAL`	`60000`	Metrics export interval in milliseconds
`OPENCODE_OTLP_LOGS_INTERVAL`	`5000`	Logs export interval in milliseconds
`OPENCODE_METRIC_PREFIX`	`opencode.`	Prefix for all metric names (e.g. set to `claude_code.` for Claude Code dashboard compatibility)
`OPENCODE_DISABLE_METRICS`	(unset)	Comma-separated list of metric name suffixes to disable (e.g. `cache.count,session.duration`)
`OPENCODE_OTLP_HEADERS`	(unset)	Comma-separated `key=value` headers added to all OTLP exports. Keep out of version control — may contain sensitive auth tokens.
`OPENCODE_RESOURCE_ATTRIBUTES`	(unset)	Comma-separated `key=value` pairs merged into the OTel resource. Example: `service.version=1.2.3,deployment.environment=production`

Quick start

export OPENCODE_ENABLE_TELEMETRY=1
export OPENCODE_OTLP_ENDPOINT=http://localhost:4317
opencode

Headers and resource attributes

# Auth token for a managed collector (e.g. Honeycomb, Grafana Cloud)
export OPENCODE_OTLP_HEADERS="x-honeycomb-team=your-api-key,x-honeycomb-dataset=opencode"

# Tag every metric and log with deployment context
export OPENCODE_RESOURCE_ATTRIBUTES="service.version=1.2.3,deployment.environment=production"

Security note: OPENCODE_OTLP_HEADERS typically contains auth tokens. Set it in your shell profile (~/.zshrc, ~/.bashrc) or a secrets manager — never commit it to version control or print it in CI logs.

Disabling specific metrics

Use OPENCODE_DISABLE_METRICS to suppress individual metrics. The value is a comma-separated list of metric name suffixes (without the prefix).

Disabling a metric only stops the counter/histogram from being incremented — the corresponding log events are still emitted.

# Disable a single metric
export OPENCODE_DISABLE_METRICS="retry.count"

# Disable multiple metrics
export OPENCODE_DISABLE_METRICS="cache.count,session.duration,session.token.total,session.cost.total,model.usage,retry.count,message.count"

opencode-only metrics

The following metrics are specific to opencode and have no equivalent in Claude Code's built-in monitoring. If you are using a Claude Code dashboard and want to avoid cluttering it with opencode-only metrics, you can disable them:

export OPENCODE_DISABLE_METRICS="cache.count,session.duration,session.token.total,session.cost.total,model.usage,retry.count,message.count"

Metric suffix	Why it's opencode-only
`cache.count`	Tracks cache read/write activity as occurrence counts — not a Claude Code signal
`session.duration`	Session wall-clock duration — not emitted by Claude Code
`session.token.total`	Per-session token histogram — not emitted by Claude Code
`session.cost.total`	Per-session cost histogram — not emitted by Claude Code
`model.usage`	Per-model message counter — not emitted by Claude Code
`retry.count`	API retry counter — not emitted by Claude Code
`message.count`	Completed message counter — not emitted by Claude Code

Datadog example

export OPENCODE_ENABLE_TELEMETRY=1
export OPENCODE_OTLP_ENDPOINT=https://api.datadoghq.com

Honeycomb example

export OPENCODE_ENABLE_TELEMETRY=1
export OPENCODE_OTLP_ENDPOINT=https://api.honeycomb.io

Claude Code dashboard compatibility

export OPENCODE_METRIC_PREFIX=claude_code.

Local development

See CONTRIBUTING.md.