Crate opentelemetry_zipkin[][src]

Expand description

OpenTelemetry Zipkin

Collects OpenTelemetry spans and reports them to a given Zipkin collector endpoint. See the Zipkin Docs for details and deployment information.

Compiler support: requires rustc 1.46+


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, TraceError};
use opentelemetry::global;

fn main() -> Result<(), TraceError> {
    let tracer = opentelemetry_zipkin::new_pipeline().install_simple()?;

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

    global::shutdown_tracer_provider(); // sending remaining spans



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) or surf-client features if you are in the tokio or async-std ecosystems respectively, or select whichever client you prefer as shown below.

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.

use opentelemetry::{KeyValue, trace::Tracer};
use opentelemetry::sdk::{trace::{self, IdGenerator, Sampler}, Resource};
use opentelemetry::sdk::export::trace::ExportResult;
use opentelemetry::global;
use opentelemetry_http::{HttpClient, HttpError};
use async_trait::async_trait;
use bytes::Bytes;
use futures_util::io::AsyncReadExt as _;
use http::{Request, Response};
use std::convert::TryInto as _;
use std::error::Error;

// `reqwest` and `surf` are supported through features, if you prefer an
// alternate http client you can add support by implementing `HttpClient` as
// shown here.
struct IsahcClient(isahc::HttpClient);

impl HttpClient for IsahcClient {
    async fn send(&self, request: Request<Vec<u8>>) -> Result<Response<Bytes>, HttpError> {
        let mut response = self.0.send_async(request).await?;
        let status = response.status();
        let mut bytes = Vec::with_capacity(response.body().len().unwrap_or(0).try_into()?);
        isahc::AsyncReadResponseExt::copy_to(&mut response, &mut bytes).await?;


fn main() -> Result<(), Box<dyn Error + Send + Sync + 'static>> {
    let tracer = opentelemetry_zipkin::new_pipeline()
                .with_resource(Resource::new(vec![KeyValue::new("key", "value")])),

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

    global::shutdown_tracer_provider(); // sending remaining spans


Crate Feature Flags

The following crate feature flags are available:

  • reqwest-blocking-client: Export spans using the reqwest blocking http client (enabled by default).
  • reqwest-client: Export spans using the reqwest non-blocking http client.
  • surf-client: Export spans using the surf non-blocking http client.

Supported Rust Versions

OpenTelemetry is built against the latest stable release. The minimum supported version is 1.46. 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.49, 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.


Zipkin span exporter

Extracts and injects SpanContexts into Extractors or Injectors using B3 header format.

Builder for ExporterConfig struct.


B3Encoding is a bitmask to represent B3 encoding type

Wrap type for errors from opentelemetry zipkin


Create a new Zipkin exporter pipeline builder.