Skip to content

feat(opencode): OpenTelemetry via @devtheops/opencode-plugin-otel - #2186

Merged
openbao-service-broker[bot] merged 1 commit into
developfrom
feature/opencode-otel
Sep 18, 2026
Merged

openbao-service-broker[bot] merged 1 commit into
developfrom
feature/opencode-otel

Conversation

@openbao-service-broker

Copy link
Copy Markdown
Contributor

OpenCode has no native OTEL support (verified against opencode.ai/docs and
open feature requests anomalyco/opencode#14246, #14697). This wires it
through the third-party plugin @devtheops/opencode-plugin-otel instead,
sharing the one existing telemetry surface (userConfig.telemetry) that
Claude Code and Codex already use.

The plugin exposes exactly one OTLP endpoint for all three signals
(metrics/logs/traces together), so this consumer targets otlpEndpoint
only and validates the signal-specific endpoints against it:

  • metricsEndpoint disagreeing with otlpEndpoint refuses the whole
    plugin (the plugin has no per-signal metrics disable).
  • tracesEndpoint disagreeing just turns traces off (the plugin does
    support a whole-signal trace disable).

New otelPluginEntries introspection option mirrors Codex's
otelExporterKinds, for the regression checks in opencode-otel-wiring.

Verification: nix flake check --accept-flake-config (native aarch64-darwin)
passes clean. --all-systems evaluates every x86_64-linux check including
the new one; building them requires a remote Linux builder this Mac doesn't
have configured -- a pre-existing environment limitation affecting every
x86_64-linux check in the flake, not introduced by this change (confirmed:
autonomous-profile-render, an unrelated pre-existing check, fails the same
way on unmodified develop).

🤖 Generated with Claude Code

https://claude.ai/code/session_014VKod2GevZsQJ7Z3HYez9a

OpenCode has no native OTEL support (verified against opencode.ai/docs and
anomalyco/opencode#14246, #14697 -- both open feature requests). Wires the
one existing telemetry surface (userConfig.telemetry) through the
third-party plugin instead, sharing the same otlpEndpoint Claude Code and
Codex already use.

The plugin exposes exactly one OTLP endpoint for all three signals, so
metrics/traces are validated against otlpEndpoint rather than routed
independently: a metricsEndpoint that disagrees refuses the whole plugin
(no per-signal metrics disable exists), a tracesEndpoint that disagrees
just turns traces off (the plugin does support a whole-signal trace
disable). tracesEndpoint always carries the full /v1/traces path
(maintainer-profile.nix), so 'agrees with otlpEndpoint' means equal to
otlpEndpoint + '/v1/traces', not string-equal to otlpEndpoint itself --
the regression test caught this before it shipped wrong.

New otelPluginEntries introspection option mirrors codex's
otelExporterKinds; it's readOnly with no default, since a readOnly option
can only take its value from exactly one definition site (mirrors
lspEnabled/mcpServerNames, not otel-plugin's own [] default which
collided with default.nix's assignment).

Assisted-by: Claude:claude-sonnet-5
Claude-Session: https://claude.ai/code/session_014VKod2GevZsQJ7Z3HYez9a
@openbao-service-broker
openbao-service-broker Bot merged commit cbd2ac1 into develop Sep 18, 2026
29 checks passed
@openbao-service-broker
openbao-service-broker Bot deleted the feature/opencode-otel branch September 18, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant