Skip to content

Deprecate Zipkin exporter #4715

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
+18 −6
Open

Deprecate Zipkin exporter #4715

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f81bd0c
Deprecate zipkin exporter
lmolkova Oct 29, 2025
c2a913b
clean up and lint
lmolkova Nov 3, 2025
e053411
Merge branch 'main' into deprecate-zipkin
lmolkova Nov 3, 2025
097163a
deprecate env vars, add changelog
lmolkova Nov 7, 2025
3e3cd00
Merge branch 'main' into deprecate-zipkin
lmolkova Nov 7, 2025
e2b9726
up
lmolkova Nov 7, 2025
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
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@ release.

### Traces

- Deprecate Zipkin exporter document and make exporter implementation optional
Copy link
Member

@pellared pellared Nov 8, 2025

Choose a reason for hiding this comment

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

Suggested change
- Deprecate Zipkin exporter document and make exporter implementation optional
- Deprecate Zipkin exporter document and make exporter implementation optional.

([#4715](https://github.com/open-telemetry/opentelemetry-specification/pull/4715/))

### Metrics

- `AlignedHistogramBucketExemplarReservoir` SHOULD use a time-weighted algorithm.
Expand Down
4 changes: 2 additions & 2 deletions spec-compliance-matrix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -334,8 +334,8 @@ Disclaimer: Declarative configuration is currently in Development status - work
| **[Zipkin](specification/trace/sdk_exporters/zipkin.md)** | Optional | Go | Java | JS | Python | Ruby | Erlang | PHP | Rust | C++ | .NET | Swift |
| Zipkin V1 JSON | X | - | + | | + | - | - | - | - | - | - | - |
| Zipkin V1 Thrift | X | - | + | | [-][py1174] | - | - | - | - | - | - | - |
| Zipkin V2 JSON | * | + | + | | + | + | - | + | + | + | + | + |
Copy link
Member

@pellared pellared Nov 8, 2025

Choose a reason for hiding this comment

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

* is no longer used.

Should we remove the following?

opentelemetry-specification/spec-compliance-matrix.md

Lines 11 to 13 in d5cfbdf

feature is required, and columns marked with `*` mean that for each type of
exporter (OTLP and Zipkin), implementing at least one of the supported
formats is required. Implementing more than one format is optional.

| Zipkin V2 Protobuf | * | - | + | | + | - | + | - | - | - | - | - |
| Zipkin V2 JSON | X | + | + | | + | + | - | + | + | + | + | + |
| Zipkin V2 Protobuf | X | - | + | | + | - | + | - | - | - | - | - |
| Service name mapping | | + | + | + | + | + | + | + | + | + | + | + |
| SpanKind mapping | | + | + | + | + | + | + | + | + | + | + | + |
| InstrumentationLibrary mapping | | + | + | - | + | + | - | + | + | + | + | + |
Expand Down
4 changes: 2 additions & 2 deletions spec-compliance-matrix/template.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -375,9 +375,9 @@ sections:
- name: Zipkin V1 Thrift
optional: true
- name: Zipkin V2 JSON
optional_one_of_group_is_required: true
optional: true
- name: Zipkin V2 Protobuf
optional_one_of_group_is_required: true
optional: true
- name: Service name mapping
- name: SpanKind mapping
- name: InstrumentationLibrary mapping
Expand Down
2 changes: 2 additions & 0 deletions specification/configuration/sdk-environment-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,8 @@ See [OpenTelemetry Protocol Exporter Configuration Options](../protocol/exporter

## Zipkin Exporter

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

| Name | Description | Default | Type |
|-------------------------------|------------------------------------------------------------------------------------|--------------------------------------|-------------|
| OTEL_EXPORTER_ZIPKIN_ENDPOINT | Endpoint for Zipkin traces | `http://localhost:9411/api/v2/spans` | [String][] |
Expand Down
11 changes: 9 additions & 2 deletions specification/trace/sdk_exporters/zipkin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,14 @@ linkTitle: Zipkin

# OpenTelemetry to Zipkin Transformation

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

_Note: This document remains here for backwards compatibility and
will be removed in a future version. SDKs MAY include Zipkin exporters,
but Zipkin exporter is not required.

Users may export to Zipkin using [zipkin exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/zipkinexporter) collector component or [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)
Zipkin server module_
Comment on lines +9 to +14
Copy link
Member

@pellared pellared Nov 8, 2025

Choose a reason for hiding this comment

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

This is not properly formatted.

Maybe

Suggested change
_Note: This document remains here for backwards compatibility and
will be removed in a future version. SDKs MAY include Zipkin exporters,
but Zipkin exporter is not required.
Users may export to Zipkin using [zipkin exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/zipkinexporter) collector component or [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)
Zipkin server module_
> Note: This document remains here for backwards compatibility and
> will be removed in a future version. SDKs MAY include Zipkin exporters,
> but Zipkin exporter is not required.
>
> Users may export to Zipkin using [zipkin exporter](https://github.com/open-telemetry/opentelemetry-collector->contrib/tree/main/exporter/zipkinexporter) collector component or [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)
>Zipkin server module.

or

Suggested change
_Note: This document remains here for backwards compatibility and
will be removed in a future version. SDKs MAY include Zipkin exporters,
but Zipkin exporter is not required.
Users may export to Zipkin using [zipkin exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/zipkinexporter) collector component or [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)
Zipkin server module_
_Note: This document remains here for backwards compatibility and
will be removed in a future version. SDKs MAY include Zipkin exporters,
but Zipkin exporter is not required.
Users may export to Zipkin using [zipkin exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/zipkinexporter) collector component or [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)
Zipkin server module._


This document defines the transformation between OpenTelemetry and Zipkin Spans.
The generic transformation [rules specified here](../../common/mapping-to-non-otlp.md) also apply. If a
Expand Down Expand Up @@ -69,7 +76,7 @@ not work properly. OpenTelemetry doesn't provide this consistency guarantee.
Exporter may chose to override the value for service name based on a local root
span to improve Zipkin user experience.

*Note*, the attribute `service.namespace` MUST NOT be used for the Zipkin
_Note_, the attribute `service.namespace` MUST NOT be used for the Zipkin
Copy link
Member

@pellared pellared Nov 8, 2025

Choose a reason for hiding this comment

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

Not seen such way of adding notes anywhere else. Maybe just (or revert)

Suggested change
_Note_, the attribute `service.namespace` MUST NOT be used for the Zipkin
Note that the attribute `service.namespace` MUST NOT be used for the Zipkin

service name and should be sent as a Zipkin tag.

### SpanKind
Expand Down
Loading