Deprecate Zipkin exporter by lmolkova · Pull Request #4715 · open-telemetry/opentelemetry-specification (original) (raw)

lmolkova changed the title[DO NOT MERGE] Deprecate Zipkin exporter Deprecate Zipkin exporter

Nov 7, 2025

Co-authored-by: Robert Pająk pellared@hotmail.com

Merged via the queue into open-telemetry:main with commit 3e09510

Nov 21, 2025

6 of 7 checks passed

This was referenced

Nov 21, 2025

github-merge-queue Bot pushed a commit that referenced this pull request

Dec 12, 2025

Context

• Make the W3C randomness flag required.

(#4761)

Traces

• Deprecate Zipkin exporter document and make exporter implementation optional.

(#4715)

• Add spec for AlwaysRecord sampler

(#4699)

Metrics

• Stabilize Enabled API for synchronous instruments.

(#4746)

• Allow instrument Enabled implementation to have additional optimizations and features.

(#4747)

Logs

• Stabilize LogRecordProcessor.Enabled.

(#4717)

SDK Configuration

• Clarifies that guidance related to boolean environment variables is not applicable to other configuration interfaces. (#4723)

Co-authored-by: Armin Ruech 7052238+arminru@users.noreply.github.com

This was referenced

Jan 13, 2026

github-merge-queue Bot pushed a commit that referenced this pull request

Mar 19, 2026

Summary

Deprecate OpenTracing compatibility requirements in the specification as Stage 1 of issue #4849.

This PR changes the OpenTracing compatibility spec document status to deprecated, adds a deprecation note, and updates wording to make it explicit that new OpenTracing compatibility implementations are no longer required by this specification.

What changed

• specification/compatibility/opentracing.md
  • Status changed from Stable to Deprecated
  • Added top-level deprecation note:
    • OpenTracing compatibility requirements are deprecated
    • existing shims MAY continue for backwards compatibility
    • new compatibility implementations are not required
    • removal criteria/timeline deferred to a separate discussion
• Updated one normative paragraph to historical framing, aligned with deprecation
• Added explicit sentence that this section remains for migration/backwards compatibility guidance
• CHANGELOG.md
• Added Unreleased/Compatibility entry for deprecating OpenTracing compatibility requirements

Context and precedent

• Addresses: #4849
• Follows the staged approach discussed in #4849 comments
• Uses the same deprecation pattern/intent as prior deprecation work in #4715 (Zipkin exporter)

Scope

This PR is intentionally narrow (Stage 1 only): deprecate requirements in spec text.

Non-goals

• No immediate removal of OpenTracing compatibility content
• No language-specific implementation mandates
• No removal timeline policy in this PR (to be handled in follow-up discussion)

Validation

Local checks run:

• make markdownlint ✅
• make markdown-toc && git diff --exit-code ':*.md' ✅
• make cspell ✅

Not run locally due environment limitation:

• make markdown-link-check (requires Docker daemon)

Notes for reviewers

This is documentation/spec wording only and does not introduce API/SDK interfaces.

Co-authored-by: Amol Patil 9298683+adp2201@users.noreply.github.com Co-authored-by: Carlos Alberto Cortez calberto.cortez@gmail.com

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})