Skip to content

Milestones

List view

  • HTTP / DB Semantic Conventions Migration

    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 closed
    96% complete1 open26 closed

  • Future Major Versions

    This is for breaking changes to be made after SDK 2.0

    No due date
    •1/7 issues closed
    14% complete6 open1 closed

  • Logs API/SDK GA

    Both 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
    •25/32 issues closed
    78% complete7 open25 closed

  • OTLP Exporter GA

    Exporters 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
    •33/41 issues closed
    80% complete8 open33 closed

  • Metrics After GA

    No due date
    •5/11 issues closed
    45% complete6 open5 closed

  • Configs

    No due date
    •16/16 issues closed
    100% complete0 open16 closed