opentelemetry-exporter-zipkin
Zipkin Span Exporters for OpenTelemetry
Decision gist · record as of 2026-08-14
Yes, if you need Zipkin trace export from Python and haven't yet decided between JSON and protobuf serialization. The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a safe choice. However, once you've settled on a serialization method, consider switching to the specific exporter package to reduce dependencies.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; Zipkin backend must be running and accessible at the configured endpoint.
- Low friction installation with a pure-Python wheel.
- Actively maintained as of 2026-07-16 with recent release activity (29 days old).
License · maintenance · safety
Apache-2.0 (permissive) — Licensed under Apache-2.0 (permissive), allowing use in commercial and proprietary projects with minimal restrictions.
last release 2026-07-16 (29 days) · last repo commit 2026-08-14 · 2,588 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 215,440 downloads/mo, #9,400 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-exporter-zipkin
from opentelemetry.exporter.zipkin.json import ZipkinExporter
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import SimpleSpanProcessor
zipkin_exporter = ZipkinExporter(localServiceName="my-service")
TracerProvider().add_span_processor(SimpleSpanProcessor(zipkin_exporter))- Whether the bundle's convenience trade-off (installing both JSON and proto-HTTP exporters) is worth the extra dependencies for typical use cases.
- Performance characteristics and overhead of the exporters when handling high-volume trace data.
What it is and what it does
This package is a convenience installer that bundles two OpenTelemetry Zipkin exporters: one using JSON serialization and one using protobuf over HTTP. It simplifies initial setup by installing both formats at once, though the documentation recommends switching to the specific exporter package once you've chosen your serialization method to avoid unnecessary dependencies.
It integrates with OpenTelemetry's standard tracer provider and span processor architecture, allowing you to export distributed trace spans to a Zipkin backend for visualization and analysis. The package itself is a thin wrapper; the actual export logic lives in its two runtime dependencies.
Use it for
- Set up distributed tracing in a Python service to send spans to a Zipkin backend for observability.
- Quickly prototype trace export configuration before committing to a specific serialization format.
- Integrate OpenTelemetry tracing into existing Python applications that already use Zipkin for monitoring.
- Export traces from microservices to a centralized Zipkin instance for cross-service request tracing.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need Zipkin trace export from Python and haven't yet decided between JSON and protobuf serialization.
The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a safe choice. However, once you've settled on a serialization method, consider switching to the specific exporter package to reduce dependencies.
Install
opentelemetry-exporter-zipkin on PyPI
Before you install
Low friction installation with a pure-Python wheel. Actively maintained as of 2026-07-16 with recent release activity (29 days old). Requires Python 3.10 or later.
Requires Python 3.10 or later; Zipkin backend must be running and accessible at the configured endpoint.
License in practice
Licensed under Apache-2.0 (permissive), allowing use in commercial and proprietary projects with minimal restrictions.
Quickstart
pip install opentelemetry-exporter-zipkin
from opentelemetry.exporter.zipkin.json import ZipkinExporter
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import SimpleSpanProcessor
zipkin_exporter = ZipkinExporter(localServiceName="my-service")
TracerProvider().add_span_processor(SimpleSpanProcessor(zipkin_exporter))Verify before relying
- Whether the bundle's convenience trade-off (installing both JSON and proto-HTTP exporters) is worth the extra dependencies for typical use cases.
- Performance characteristics and overhead of the exporters when handling high-volume trace data.
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesopentelemetry-exporter-zipkin-jsonopentelemetry-exporter-zipkin-proto-http |
| Maintenance | Actively maintained 29 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 215,440 / month, #9,400 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableFramework :: OpenTelemetryFramework :: OpenTelemetry :: ExportersIntended Audience :: DevelopersProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Typing :: Typed |
Evidence: opentelemetry_exporter_zipkin-1.44.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “span exporter setup”
- opentelemetry-exporter-zipkinInstalls a convenience bundle of OpenTelemetry Zipkin exporters (JSON…
- arize-otelWraps OpenTelemetry with Arize-aware defaults to instrument and send…
- opentelemetry-exporter-zipkin-jsonExports OpenTelemetry tracing data to Zipkin using JSON serialization…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also opentelemetry-exporter-zipkin-json · opentelemetry-exporter-zipkin-proto-http · py-zipkin · opentelemetry-exporter-otlp · opentelemetry-exporter-jaeger · opentelemetry-exporter-otlp-proto-grpc · opentelemetry-exporter-prometheus · opentelemetry-exporter-otlp-proto-common · azure-monitor-opentelemetry-exporter