Skip to content

Deprecate OpenCensus compatibility requirements#5138

Merged
jack-berg merged 4 commits into
open-telemetry:mainfrom
Krishnachaitanyakc:fix/5109-deprecate-opencensus
Jun 12, 2026
Merged

Deprecate OpenCensus compatibility requirements#5138
jack-berg merged 4 commits into
open-telemetry:mainfrom
Krishnachaitanyakc:fix/5109-deprecate-opencensus

Conversation

@Krishnachaitanyakc

Copy link
Copy Markdown
Contributor

Deprecate OpenCensus compatibility requirements, following the same pattern as the OpenTracing deprecation in #4938.

OpenCensus was sunset in July 2023. Adoption numbers are microscopic (JS: 31/week npm; Python: ~225/week PyPI; no .NET or Rust shim shipped). @jack-berg confirmed he is happy to sponsor.

Changes:

  • specification/compatibility/opencensus.md: status → Deprecated; added NOTE block with June 2027 removal timeline
  • CHANGELOG.md: Unreleased → Compatibility entry

Fixes #5109

OpenCensus is no longer maintained (sunsetting blog post July 2023).
Adoption numbers across language implementations are microscopic
(JS: 31/week npm; Python: ~225/week PyPI; no .NET or Rust shim).

This follows the same pattern as the OpenTracing deprecation in open-telemetry#4938:
mark the status as Deprecated, add a NOTE block with the timeline
(no earlier than June 2027), and preserve the existing content for
migration guidance.

Fixes open-telemetry#5109
@thompson-tomo

Copy link
Copy Markdown
Contributor

Should we also be adding a note to https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md under the OpenCensus section?

@Krishnachaitanyakc
Krishnachaitanyakc requested a review from a team as a code owner June 8, 2026 17:44

@jack-berg jack-berg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Krishnachaitanyakc! In continuation of following the pattern of the opentracing compatibility document, we should also publish a quick blog post to share the change more widely.

See:

@Krishnachaitanyakc

Copy link
Copy Markdown
Contributor Author

Thanks @jack-berg. I will open the follow-up blog PR after this merges

@jack-berg

Copy link
Copy Markdown
Member

I'll merge this on Friday 6/12 if there are no dissenting opinions.

@jack-berg
jack-berg added this pull request to the merge queue Jun 12, 2026
Merged via the queue into open-telemetry:main with commit 3021772 Jun 12, 2026
9 checks passed
@carlosalberto carlosalberto mentioned this pull request Jun 18, 2026
jack-berg pushed a commit to cijothomas/opentelemetry-specification that referenced this pull request Jun 22, 2026
### Context

- Clarify that environment variable propagation carriers normalize
requested
  keys, carrier keys, and returned keys.

([open-telemetry#5102](open-telemetry#5102))
- Specify that environment variable propagation carriers only read and
return
  normalized environment variable names.

([open-telemetry#5144](open-telemetry#5144))
- Specify that an empty environment variable propagation name is
non-normalized
  and normalizes to `_`.

([open-telemetry#5163](open-telemetry#5163))

### Profiles

- Remove duplicate information from and extend Profiles documentation
(README.md, pprof.md).

([open-telemetry#4932](open-telemetry#4932))

### Entities

- Add specification for communicating entity information as structured
log events.

([open-telemetry#4836](open-telemetry#4836))

### Common

- Add an in-development [SDK
self-observability](specification/self-observability.md)
  section, referenced from the Tracing, Metrics, and Logs SDK specs.

([open-telemetry#5087](open-telemetry#5087))
- Clarify non-OTLP representation guidance for nested `AnyValue` values
in
  arrays and maps.

([open-telemetry#5053](open-telemetry#5053))
- Add in-development guidance recommending a JSON object as the string
  representation for an attribute in non-OTLP protocols.

([open-telemetry#5028](open-telemetry#5028))
- Add in-development guidance recommending a JSON object as the string
  representation for an attribute collection in non-OTLP protocols.

([open-telemetry#5110](open-telemetry#5110))

### Compatibility

- Deprecate OpenCensus compatibility requirements in the specification.

([open-telemetry#5138](open-telemetry#5138))
- Stabilize sections of Prometheus Metrics Exporter.
  - Clarify resource attributes configuration.

([open-telemetry#5084](open-telemetry#5084))
- Stabilize the conversion of OTLP Summaries into Prometheus Summaries.

([open-telemetry#5107](open-telemetry#5107))
  - Stabilize client libs section.

([open-telemetry#5106](open-telemetry#5106))
- Stabilize Prometheus Metrics Exporter default aggregation
configuration.

([open-telemetry#5113](open-telemetry#5113))
- Stabilize sections of Prometheus and OpenMetrics Compatibility.
- Stabilize OpenTelemetry Histogram to Prometheus Histogram
transformation.

([open-telemetry#5091](open-telemetry#5091))
- Add optional OpenTelemetry Histogram to Prometheus Native Histogram
with Custom Buckets transformation.

([open-telemetry#5091](open-telemetry#5091))

### SDK Configuration

- Add link to declarative config IdGenerator type

([open-telemetry#5133](open-telemetry#5133))

### OTEPs

- Context-scoped Attributes.

([open-telemetry#4931](open-telemetry#4931))

---------

Co-authored-by: Reiley Yang <reyang@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Opencensus / Opencensus shim deprecation