List view
This is the OTel JS milestone for completing the migration to stable HTTP and database semconv. The OpenTelemetry plan is described by: - https://opentelemetry.io/docs/specs/semconv/non-normative/http-migration/ - https://opentelemetry.io/docs/specs/semconv/non-normative/db-migration/ See https://github.com/open-telemetry/opentelemetry-js/blob/main/doc/semconv-stable-http-and-database.md for full OTel JS details. tl;dr: The plan supports a rougly 6-month period during which users can configure instrumentations (via `OTEL_SEMCONV_STABILITY_OPT_IN`) to emit old and stable semconv (span attributes, mostly), and then migration their downstream usage (dashboards, etc.) to the stable semconv. In 2026-01 all relevant `@opentelemetry/instrumentation-*` packages will support this. Around 2026-06 (in conjunction with an OTel JS SDK v3) the migration period will be considered complete, default behaviour will use the stable semconv and `OTEL_SEMCONV_STABILITY_OPT_IN` support will be removed.
No due date•26/27 issues closedThis is for breaking changes to be considered/made for OTel JS SDK 3.0. The expected major change in v3 will be dropping support for Node.js 18 and 20. There is no promised release date, but we expect something in June/July 2026 -- after 2026-04-30, when Node.js v20.x goes EOL.
No due date•2/11 issues closedBoth Logs API and SDK are currently experimental and not stable, This milestone is for tracking issues that need to be completed for GA/stable release.
No due date•39/44 issues closedExporters are currently still marked as experimental. This milestone is for tracking issues that need to be completed for an OTLP exporter GA release.
No due date•35/41 issues closed- No due date•5/11 issues closed
- No due date•16/16 issues closed