otel-sdk-versions
OpenTelemetry SDK Versions
Use this skill when you need the latest released OpenTelemetry SDK or package version for a language.
Workflow
- Open
references/generated/otel-version-index.md.
- identify the row for the project language and package
- use the bundled table as the default source of truth for supported languages in this repository
- Choose the version deliberately.
- prefer the latest released version when it is compatible with the project
- if the latest release is not compatible, choose the latest compatible version and state the compatibility reason explicitly
- reuse that decision for the rest of the task unless the language, package, or constraints change
- Resolve companion packages from the release source.
- the index covers one primary SDK package per language
- if the task requires additional packages from the same ecosystem (exporters, instrumentations, resource detectors), look up their versions from the release source — do not infer or reuse the primary package version
- sub-packages within the same project often share a version line but not always; confirm each package individually
- Use the linked follow-up sources when needed.
- use the Release Source column to confirm the package or repo
- use the Setup Docs column for SDK setup guidance
- use the Examples column for implementation references when examples are available
- Handle gaps explicitly.
- if the requested language or package is not in the bundled index, say that the index does not cover that exact package
- then fall back to the official release source and official docs for that package
- do not assume an unreleased, prerelease, or incompatible version is acceptable without saying so
More from ollygarden/opentelemetry-agent-skills
sdk-setup
OpenTelemetry SDK initialization and configuration. Use when setting up or reviewing TracerProvider, MeterProvider, or LoggerProvider; choosing exporters, processors, or propagators; configuring OTLP transport; or extending an existing SDK setup for new signals. Use this skill whenever the task involves wiring up the OpenTelemetry SDK, even if the user only mentions "add tracing" or "set up metrics" without saying "SDK.
8telemetrygen
Construct telemetrygen commands for generating synthetic OpenTelemetry traces, metrics, and logs via OTLP. Use this skill whenever the user wants to generate test telemetry, load test a collector or backend, create synthetic OTLP data, send sample traces/metrics/logs to an endpoint, test collector pipelines or processors, validate OTTL transforms, test tail sampling, or mentions telemetrygen in any context. Also trigger when the user asks how to simulate telemetry traffic, stress test an observability stack, or produce sample data for dashboards.
8sdk-versions
OpenTelemetry SDK and package version lookup across languages. Use when choosing the latest compatible released OpenTelemetry SDK or package version and locating setup docs or examples.
8semantic-conventions
OpenTelemetry semantic convention lookup and naming guidance. Use when selecting released semantic convention groups, attributes, or span naming rules, or when checking semantic convention compliance.
8manual-instrumentation
OpenTelemetry best practices for manual instrumentation. Use when adding, changing, or reviewing OpenTelemetry instrumentation in code. Guidance to choose runtime boundaries, choose signals, apply semantic conventions, handle propagation, control cardinality, and verify the result.
8span-events-to-logs-migration
Migrate OpenTelemetry Span Events (AddEvent, RecordException) to the Logs API following the OTEP 4430 deprecation plan. Use when migrating instrumentation from span events to log-based events, reviewing code that still uses AddEvent or RecordException, or planning a migration across a codebase.
8