opentelemetry-tide 0.5.2

OpenTelemetry integration for Tide
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

use opentelemetry::global;
use opentelemetry::sdk::propagation::{
    B3Encoding, B3Propagator, BaggagePropagator, JaegerPropagator, TextMapCompositePropagator, TraceContextPropagator,
};

pub fn init_global_propagator() {
    global::set_text_map_propagator(composite_propagator());
    // OR you could use a single propagator only:
    // global::set_text_map_propagator(TraceContextPropagator::new());
}

fn composite_propagator() -> TextMapCompositePropagator {
    // the good old zipkin format - probably useful for zipkin environments only
    let b3_propagator = B3Propagator::with_encoding(B3Encoding::SingleAndMultiHeader);

    // W3C spec: https://w3c.github.io/baggage/ - very flexible KV format, can carry more than just trace context data
    let baggage_propagator = BaggagePropagator::new();

    // Uber's original format - probably only useful in a closed jaeger only setup
    let jaeger_propagator = JaegerPropagator::new(); // aka Uber headers

    // Yet another W3C spec: https://www.w3.org/TR/trace-context/ - only for trace context info
    let trace_context_propagator = TraceContextPropagator::new();

    // NB! last wins (and overwrites!); so re-order based on your actual usage or preferences
    // or leave out propagators you definitely do no use;
    // of course, if you send all headers with identical values the order doesn't matter.
    TextMapCompositePropagator::new(vec![
        Box::new(jaeger_propagator),
        Box::new(b3_propagator),
        Box::new(baggage_propagator),
        Box::new(trace_context_propagator),
    ])
}

// make rust (analyzer) happy
#[allow(dead_code)]
fn main() {}