← ClaudeAtlas

language-maturitylisted

Per-language OTel signal maturity matrix (Stable / Beta / Development) and feature-gating rules. Use before generating OTel SDK code to gate signals by maturity and the --experimental flag.
radra23/otel-as-code-plugin · ★ 1 · Data & Documents · score 70
Install: claude install-skill radra23/otel-as-code-plugin
# OTel Language Signal Maturity Matrix Reference: opentelemetry.io/docs/languages (pinned semconv version: see `SEMCONV_VERSION` in the `semconv-discipline` skill — the single source of truth) ## Maturity Levels - **Stable** — API/SDK frozen, safe for production, full semconv coverage - **Beta** — feature-complete but may have minor API changes - **Development** — experimental, incomplete, not for production ## Runtime gating — what this matrix is about Every row below describes a **server-side runtime**. The matrix is indexed by the service's `runtime` field from the context cache, NOT by `language`: those are different questions, and conflating them is how a Vite + React SPA (`language: nodejs`, `runtime: browser`) gets a `@opentelemetry/sdk-node` bootstrap that cannot run and breaks the build. | `runtime` | In scope? | Notes | |-----------|-----------|-------------------------------------------------------------------| | `node` | yes | Node.js row below | | `python` | yes | Python row below | | `jvm` | yes | Java agent row below | | `dotnet` | yes | .NET code-based SDK (all signals Stable) — see the .NET row below | | `browser` | **no** | Out of scope for the MVP — see "Browser / RUM" below | | `go` | yes | Go