From 9b09018bfd6a021060d40d1bd2cf935afc6251d4 Mon Sep 17 00:00:00 2001 From: Amol Patil <9298683+adp2201@users.noreply.github.com> Date: Wed, 11 Mar 2026 15:38:05 -0700 Subject: [PATCH 1/7] Add draft blog post for OpenTracing deprecation --- .../deprecating-opentracing-compatibility.md | 65 +++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 content/en/blog/2026/deprecating-opentracing-compatibility.md diff --git a/content/en/blog/2026/deprecating-opentracing-compatibility.md b/content/en/blog/2026/deprecating-opentracing-compatibility.md new file mode 100644 index 000000000000..971bb61025e2 --- /dev/null +++ b/content/en/blog/2026/deprecating-opentracing-compatibility.md @@ -0,0 +1,65 @@ +--- +title: Deprecating OpenTracing compatibility requirements +linkTitle: Deprecating OpenTracing compatibility +date: 2026-03-11 +author: '[Amol Patil](https://github.com/adp2201)' +draft: true +issue: 9385 +sig: Specification +cSpell:ignore: Patil +--- + +The OpenTelemetry Specification project is deprecating OpenTracing +compatibility requirements in the specification, following discussion in +[issue #4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849) +and the Stage 1 change in +[PR #4938](https://github.com/open-telemetry/opentelemetry-specification/pull/4938). + +This is a deprecation of specification requirements, not an immediate removal +of compatibility material or a mandate to remove existing shim artifacts. + +## What is changing? + +- OpenTracing compatibility requirements in the specification are deprecated. +- Implementing new OpenTracing compatibility is no longer required for new SDKs + or implementations. +- Existing OpenTracing shims can continue to be supported for backwards + compatibility during the deprecation period. + +## Why now? + +OpenTracing itself has been archived for years, and ecosystem adoption has +converged around native OpenTelemetry APIs and OTLP-based workflows. The project +also has precedent for this staged approach from prior deprecation work, such as +Zipkin exporter deprecation in +[PR #4715](https://github.com/open-telemetry/opentelemetry-specification/pull/4715). + +## Timeline and policy + +As of March 2026, the OpenTracing compatibility requirements are deprecated in +spec text. + +Removal policy and timeline are intentionally handled in follow-up discussions, +with these principles guiding the process: + +- clear migration guidance for users still on shims, +- explicit Technical Committee confirmation before removal, and +- support windows aligned with SDK stability guarantees (at least one year + after artifact deprecation). + +## What should users do? + +If you still depend on an OpenTracing shim, now is the right time to plan +migration to native OpenTelemetry APIs and SDKs. + +Start by reviewing: + +- [Migrating from OpenTracing](/docs/migration/opentracing/) +- [OpenTracing compatibility spec page](/docs/specs/otel/compatibility/opentracing/) + +## Questions and feedback + +Please share feedback in the specification repository: + +- [Issue #4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849) +- [PR #4938](https://github.com/open-telemetry/opentelemetry-specification/pull/4938) From f067d453c4ec95d88bf7ef99038e1e92622607d2 Mon Sep 17 00:00:00 2001 From: Amol Patil <9298683+adp2201@users.noreply.github.com> Date: Tue, 7 Apr 2026 17:07:42 -0700 Subject: [PATCH 2/7] Refresh OpenTracing deprecation blog post for review --- .../deprecating-opentracing-compatibility.md | 44 +++++++++++-------- 1 file changed, 25 insertions(+), 19 deletions(-) diff --git a/content/en/blog/2026/deprecating-opentracing-compatibility.md b/content/en/blog/2026/deprecating-opentracing-compatibility.md index 971bb61025e2..242a8b5e8175 100644 --- a/content/en/blog/2026/deprecating-opentracing-compatibility.md +++ b/content/en/blog/2026/deprecating-opentracing-compatibility.md @@ -1,22 +1,25 @@ --- title: Deprecating OpenTracing compatibility requirements linkTitle: Deprecating OpenTracing compatibility -date: 2026-03-11 +date: 2026-04-07 author: '[Amol Patil](https://github.com/adp2201)' -draft: true issue: 9385 sig: Specification cSpell:ignore: Patil --- -The OpenTelemetry Specification project is deprecating OpenTracing -compatibility requirements in the specification, following discussion in -[issue #4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849) -and the Stage 1 change in -[PR #4938](https://github.com/open-telemetry/opentelemetry-specification/pull/4938). +On March 19, 2026, the OpenTelemetry Specification project merged +[PR #4938](https://github.com/open-telemetry/opentelemetry-specification/pull/4938), +deprecating OpenTracing compatibility requirements in the specification. + +This change updates the specification to match where the ecosystem already is: +OpenTracing has been archived for years, and new integrations are expected to +use native OpenTelemetry APIs and SDKs instead of building on OpenTracing shim +requirements. This is a deprecation of specification requirements, not an immediate removal -of compatibility material or a mandate to remove existing shim artifacts. +of compatibility material and not a requirement to remove existing shim +artifacts right away. ## What is changing? @@ -25,6 +28,8 @@ of compatibility material or a mandate to remove existing shim artifacts. or implementations. - Existing OpenTracing shims can continue to be supported for backwards compatibility during the deprecation period. +- New work should target native OpenTelemetry APIs, SDKs, and OTLP-based + workflows instead of introducing new OpenTracing dependencies. ## Why now? @@ -36,25 +41,26 @@ Zipkin exporter deprecation in ## Timeline and policy -As of March 2026, the OpenTracing compatibility requirements are deprecated in -spec text. - -Removal policy and timeline are intentionally handled in follow-up discussions, -with these principles guiding the process: - -- clear migration guidance for users still on shims, -- explicit Technical Committee confirmation before removal, and -- support windows aligned with SDK stability guarantees (at least one year - after artifact deprecation). +- **Specification deprecation**: effective as of **March 2026**. +- **Earliest specification removal**: **no earlier than March 2027**, as stated + in the merged spec text. +- **Follow-up work**: additional migration guidance and future removal + discussions continue in + [issue #4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849). ## What should users do? If you still depend on an OpenTracing shim, now is the right time to plan migration to native OpenTelemetry APIs and SDKs. +If your current shim-based setup is stable, this announcement does not require +an immediate change. However, you should avoid introducing new dependencies on +OpenTracing compatibility and plan your migration path during the deprecation +window. + Start by reviewing: -- [Migrating from OpenTracing](/docs/migration/opentracing/) +- [Migrating from OpenTracing](/docs/compatibility/migration/opentracing/) - [OpenTracing compatibility spec page](/docs/specs/otel/compatibility/opentracing/) ## Questions and feedback From c861c354efb04f753108699da6bac6fb2342f3ef Mon Sep 17 00:00:00 2001 From: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com> Date: Thu, 9 Apr 2026 10:48:43 -0700 Subject: [PATCH 3/7] Update content/en/blog/2026/deprecating-opentracing-compatibility.md --- content/en/blog/2026/deprecating-opentracing-compatibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/2026/deprecating-opentracing-compatibility.md b/content/en/blog/2026/deprecating-opentracing-compatibility.md index 242a8b5e8175..d3408036bebb 100644 --- a/content/en/blog/2026/deprecating-opentracing-compatibility.md +++ b/content/en/blog/2026/deprecating-opentracing-compatibility.md @@ -1,7 +1,7 @@ --- title: Deprecating OpenTracing compatibility requirements linkTitle: Deprecating OpenTracing compatibility -date: 2026-04-07 +date: 2026-04-14 author: '[Amol Patil](https://github.com/adp2201)' issue: 9385 sig: Specification From a0fc05f52be70fe29957895e6ede9e991f5c615f Mon Sep 17 00:00:00 2001 From: otelbot <197425009+otelbot@users.noreply.github.com> Date: Thu, 9 Apr 2026 18:04:45 +0000 Subject: [PATCH 4/7] Results from /fix directive --- .../deprecating-opentracing-compatibility.md | 6 +++--- static/refcache.json | 16 ++++++++++++++++ 2 files changed, 19 insertions(+), 3 deletions(-) diff --git a/content/en/blog/2026/deprecating-opentracing-compatibility.md b/content/en/blog/2026/deprecating-opentracing-compatibility.md index d3408036bebb..46a2f932d6e4 100644 --- a/content/en/blog/2026/deprecating-opentracing-compatibility.md +++ b/content/en/blog/2026/deprecating-opentracing-compatibility.md @@ -17,9 +17,9 @@ OpenTracing has been archived for years, and new integrations are expected to use native OpenTelemetry APIs and SDKs instead of building on OpenTracing shim requirements. -This is a deprecation of specification requirements, not an immediate removal -of compatibility material and not a requirement to remove existing shim -artifacts right away. +This is a deprecation of specification requirements, not an immediate removal of +compatibility material and not a requirement to remove existing shim artifacts +right away. ## What is changing? diff --git a/static/refcache.json b/static/refcache.json index 55395080762c..b9a77947c42e 100644 --- a/static/refcache.json +++ b/static/refcache.json @@ -4271,6 +4271,10 @@ "StatusCode": 206, "LastSeen": "2026-03-12T09:59:44.942837566Z" }, + "https://github.com/adp2201": { + "StatusCode": 206, + "LastSeen": "2026-04-09T18:02:03.574738781Z" + }, "https://github.com/adrielp": { "StatusCode": 206, "LastSeen": "2026-03-18T09:54:42.886535103Z" @@ -15775,6 +15779,10 @@ "StatusCode": 206, "LastSeen": "2026-03-18T09:54:51.749798255Z" }, + "https://github.com/open-telemetry/opentelemetry-specification/issues/4849": { + "StatusCode": 206, + "LastSeen": "2026-04-09T18:02:20.00705171Z" + }, "https://github.com/open-telemetry/opentelemetry-specification/issues/617": { "StatusCode": 206, "LastSeen": "2026-03-12T09:59:52.264002138Z" @@ -15795,6 +15803,10 @@ "StatusCode": 206, "LastSeen": "2026-03-10T09:52:37.469361095Z" }, + "https://github.com/open-telemetry/opentelemetry-specification/pull/4715": { + "StatusCode": 206, + "LastSeen": "2026-04-09T18:02:15.253384405Z" + }, "https://github.com/open-telemetry/opentelemetry-specification/pull/4719": { "StatusCode": 206, "LastSeen": "2026-03-18T15:38:20.43438739-07:00" @@ -15807,6 +15819,10 @@ "StatusCode": 206, "LastSeen": "2026-03-18T15:38:16.556284959-07:00" }, + "https://github.com/open-telemetry/opentelemetry-specification/pull/4938": { + "StatusCode": 206, + "LastSeen": "2026-04-09T18:02:09.18182436Z" + }, "https://github.com/open-telemetry/opentelemetry-specification/pull/4947": { "StatusCode": 206, "LastSeen": "2026-03-18T15:38:22.619665266-07:00" From 36d9a76ea09cd6f848e295eed3a5a99173ed3bf5 Mon Sep 17 00:00:00 2001 From: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com> Date: Tue, 14 Apr 2026 10:58:47 -0700 Subject: [PATCH 5/7] Apply suggestion from @tiffany76 --- content/en/blog/2026/deprecating-opentracing-compatibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/2026/deprecating-opentracing-compatibility.md b/content/en/blog/2026/deprecating-opentracing-compatibility.md index 46a2f932d6e4..6af1466383c1 100644 --- a/content/en/blog/2026/deprecating-opentracing-compatibility.md +++ b/content/en/blog/2026/deprecating-opentracing-compatibility.md @@ -1,7 +1,7 @@ --- title: Deprecating OpenTracing compatibility requirements linkTitle: Deprecating OpenTracing compatibility -date: 2026-04-14 +date: 2026-04-23 author: '[Amol Patil](https://github.com/adp2201)' issue: 9385 sig: Specification From d3fce18f8f581fa0d4507c66f70c2b7de7ff7a99 Mon Sep 17 00:00:00 2001 From: Amol Patil <9298683+adp2201@users.noreply.github.com> Date: Thu, 16 Apr 2026 06:55:49 -0700 Subject: [PATCH 6/7] Address review comments on OpenTracing deprecation blog post --- .../2026/deprecating-opentracing-compatibility.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/content/en/blog/2026/deprecating-opentracing-compatibility.md b/content/en/blog/2026/deprecating-opentracing-compatibility.md index 6af1466383c1..face2c33dc94 100644 --- a/content/en/blog/2026/deprecating-opentracing-compatibility.md +++ b/content/en/blog/2026/deprecating-opentracing-compatibility.md @@ -44,28 +44,13 @@ Zipkin exporter deprecation in - **Specification deprecation**: effective as of **March 2026**. - **Earliest specification removal**: **no earlier than March 2027**, as stated in the merged spec text. -- **Follow-up work**: additional migration guidance and future removal - discussions continue in - [issue #4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849). ## What should users do? If you still depend on an OpenTracing shim, now is the right time to plan migration to native OpenTelemetry APIs and SDKs. -If your current shim-based setup is stable, this announcement does not require -an immediate change. However, you should avoid introducing new dependencies on -OpenTracing compatibility and plan your migration path during the deprecation -window. - Start by reviewing: - [Migrating from OpenTracing](/docs/compatibility/migration/opentracing/) - [OpenTracing compatibility spec page](/docs/specs/otel/compatibility/opentracing/) - -## Questions and feedback - -Please share feedback in the specification repository: - -- [Issue #4849](https://github.com/open-telemetry/opentelemetry-specification/issues/4849) -- [PR #4938](https://github.com/open-telemetry/opentelemetry-specification/pull/4938) From 65cf95790d588cd9fcc55e57ce5344882c1ae8c9 Mon Sep 17 00:00:00 2001 From: Patrice Chalin Date: Mon, 20 Apr 2026 18:03:35 -0400 Subject: [PATCH 7/7] Refresh refcache after resolving conflicts --- static/refcache.json | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/static/refcache.json b/static/refcache.json index 65dbad1e9fe2..146e0dab20fd 100644 --- a/static/refcache.json +++ b/static/refcache.json @@ -4267,6 +4267,10 @@ "StatusCode": 206, "LastSeen": "2026-04-15T10:08:19.796182501Z" }, + "https://github.com/adp2201": { + "StatusCode": 206, + "LastSeen": "2026-04-20T18:02:38.256863-04:00" + }, "https://github.com/adrielp": { "StatusCode": 206, "LastSeen": "2026-03-18T09:54:42.886535103Z" @@ -14639,6 +14643,10 @@ "StatusCode": 206, "LastSeen": "2026-04-10T10:02:48.20350632Z" }, + "https://github.com/open-telemetry/opentelemetry-specification/pull/4715": { + "StatusCode": 206, + "LastSeen": "2026-04-20T18:02:43.28731-04:00" + }, "https://github.com/open-telemetry/opentelemetry-specification/pull/4719": { "StatusCode": 206, "LastSeen": "2026-03-18T15:38:20.43438739-07:00" @@ -14651,6 +14659,10 @@ "StatusCode": 206, "LastSeen": "2026-03-18T15:38:16.556284959-07:00" }, + "https://github.com/open-telemetry/opentelemetry-specification/pull/4938": { + "StatusCode": 206, + "LastSeen": "2026-04-20T18:02:41.065759-04:00" + }, "https://github.com/open-telemetry/opentelemetry-specification/pull/4947": { "StatusCode": 206, "LastSeen": "2026-03-18T15:38:22.619665266-07:00"