20 breaking releases

0.20.0 Feb 25, 2024
0.19.0 Nov 6, 2023
0.18.0 Jul 30, 2023
0.17.0 Mar 26, 2023
0.0.1 Mar 24, 2020

#641 in Debugging

Download history 1577/week @ 2023-12-23 2150/week @ 2023-12-30 6746/week @ 2024-01-06 5756/week @ 2024-01-13 7106/week @ 2024-01-20 6902/week @ 2024-01-27 6399/week @ 2024-02-03 7224/week @ 2024-02-10 8264/week @ 2024-02-17 7384/week @ 2024-02-24 7992/week @ 2024-03-02 7639/week @ 2024-03-09 6496/week @ 2024-03-16 7897/week @ 2024-03-23 9795/week @ 2024-03-30 6828/week @ 2024-04-06

32,174 downloads per month
Used in 12 crates (6 directly)


18K SLoC

OpenTelemetry — An observability framework for cloud-native software.

OpenTelemetry Zipkin

Zipkin integration for applications instrumented with OpenTelemetry.

Crates.io: opentelemetry-zipkin Documentation LICENSE GitHub Actions CI Slack


OpenTelemetry is a collection of tools, APIs, and SDKs used to instrument, generate, collect, and export telemetry data (metrics, logs, and traces) for analysis in order to understand your software's performance and behavior. This crate provides a trace pipeline and exporter for sending span information to a Zipkin collector for processing and visualization.

Compiler support: requires rustc 1.64+


First make sure you have a running version of the zipkin process you want to send data to:

$ docker run -d -p 9411:9411 openzipkin/zipkin

Then install a new pipeline with the recommended defaults to start exporting telemetry:

use opentelemetry::trace::Tracer;
use opentelemetry::global;

fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync + 'static>> {
    let tracer = opentelemetry_zipkin::new_pipeline().install_simple()?;

    tracer.in_span("doing_work", |cx| {
        // Traced app logic here...




For optimal performance, a batch exporter is recommended as the simple exporter will export each span synchronously on drop. You can enable the rt-tokio, rt-tokio-current-thread or rt-async-std features and specify a runtime on the pipeline builder to have a batch exporter configured for you automatically.

opentelemetry = { version = "*", features = ["rt-tokio"] }
opentelemetry-zipkin = { version = "*", features = ["reqwest-client"], default-features = false }
let tracer = opentelemetry_zipkin::new_pipeline()

Choosing an HTTP client

The HTTP client that this exporter will use can be overridden using features or a manual implementation of the HttpClient trait. By default the reqwest-blocking-client feature is enabled which will use the reqwest crate. While this is compatible with both async and non-async projects, it is not optimal for high-performance async applications as it will block the executor thread. Consider using the reqwest-client (without blocking) if you are in the tokio ecosystem.

Note that async http clients may require a specific async runtime to be available so be sure to match them appropriately.

Kitchen Sink Full Configuration

Example showing how to override all configuration options. See the ZipkinPipelineBuilder docs for details of each option.

Supported Rust Versions

OpenTelemetry is built against the latest stable release. The minimum supported version is 1.64. The current OpenTelemetry version is not guaranteed to build on Rust versions earlier than the minimum supported version.

The current stable Rust compiler and the three most recent minor versions before it will always be supported. For example, if the current stable compiler version is 1.64, the minimum supported version will not be increased past 1.46, three minor versions prior. Increasing the minimum supported compiler version is not considered a semver breaking change as long as doing so complies with this policy.


~263K SLoC