Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,8 @@ release.

### Compatibility

- Deprecate OpenTracing compatibility requirements in the specification.
([#4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849))
- Stabilize Prometheus Classic Histogram to OTLP Explicit Histogram transformation.
([#4874](https://github.com/open-telemetry/opentelemetry-specification/pull/4874))
- Clarify Prometheus Native Histogram to OTLP Exponential Histogram conversion,
Expand Down
19 changes: 16 additions & 3 deletions specification/compatibility/opentracing.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,17 @@ linkTitle: OpenTracing

# OpenTracing Compatibility

**Status**: [Stable](../document-status.md).
**Status**: [Deprecated](../document-status.md)

> [!NOTE]
> OpenTracing compatibility requirements are deprecated.
> Existing OpenTracing shims MAY continue to be supported for backwards
> compatibility, but implementing new OpenTracing compatibility is not required
> by this specification.
>
> OpenTracing compatibility requirements are deprecated as of March 2026.
> OpenTracing compatibility requirements in this specification will be removed
> no earlier than March 2027.

<details>
<summary>Table of Contents</summary>
Expand Down Expand Up @@ -51,8 +61,9 @@ More specifically, the intention is to allow OpenTracing instrumentation to be
recorded using OpenTelemetry. This Shim Layer MUST NOT publicly expose any
upstream OpenTelemetry API.

This functionality MUST be defined in its own OpenTracing Shim Layer, not in the
OpenTracing nor the OpenTelemetry API or SDK.
Historically, this functionality was defined in its own OpenTracing Shim Layer,
not in the OpenTracing nor the OpenTelemetry API or SDK. Since this
compatibility is deprecated, new implementations are not required.

Semantic convention mapping SHOULD NOT be performed, with the
exception of error mapping, as described in the [Set Tag](#set-tag) and
Expand All @@ -69,6 +80,8 @@ is not recommended for the following scenarios:
semantics and may lead to incorrect `Context` usage and incorrect traces.
See [Implicit and Explicit support mismatch](#implicit-and-explicit-support-mismatch).

This section remains for migration and backwards compatibility guidance.

## Language version support

Users are encouraged to check and update their language and runtime
Expand Down
Loading