Crate dcontext_tracing 

dcontext-tracing

Automatic dcontext scope management via tracing spans.

This crate provides a tracing_subscriber::Layer that automatically creates and manages dcontext scopes when tracing spans are entered and exited. This means your context values follow the natural span lifecycle without any manual scope management.

Quick Start

use tracing_subscriber::prelude::*;

// Zero-config: every span creates a dcontext scope
tracing_subscriber::registry()
    .with(dcontext_tracing::DcontextLayer::new())
    .init();

Features

Level 1: Automatic Scoping

With zero configuration, DcontextLayer creates a new dcontext scope every time a span is entered. Values set inside a span are automatically cleaned up when the span exits, just like tracing’s own span lifecycle.

// Register context keys, then inside a span:
// dcontext::set_context("user", "alice".to_string());
// {
//     let _span = tracing::info_span!("request").entered();
//     // New scope created — inherits parent values
//     dcontext::set_context("request_id", "abc-123".to_string());
// }
// Scope reverted — "request_id" gone, "user" remains

Level 2: Field-to-Context Mapping

Map tracing span fields directly to dcontext values:

use dcontext_tracing::{DcontextLayer, FromFieldValue};
use tracing_subscriber::Registry;

#[derive(Clone, Default, Debug, serde::Serialize, serde::Deserialize)]
struct RequestId(String);

impl FromFieldValue for RequestId {
    fn from_str_value(s: &str) -> Option<Self> {
        Some(RequestId(s.to_string()))
    }
}

let layer: DcontextLayer<Registry> = DcontextLayer::builder()
    .map_field::<RequestId>("request_id")
    .build();

Level 3: Span Info

Expose span metadata as a context value:

use dcontext_tracing::{DcontextLayer, SpanInfo};
use tracing_subscriber::Registry;

let layer: DcontextLayer<Registry> = DcontextLayer::builder()
    .include_span_info()
    .build();

// Inside a span:
// let info: SpanInfo = dcontext::get_context("dcontext.span");
// info.name, info.target, info.level

How It Works

The layer uses a thread-local stack to store dcontext ScopeGuards (which are !Send and cannot be stored in tracing’s span extensions). On span enter, a new scope is pushed; on span exit, the scope is popped and the guard dropped, reverting context changes made in that scope.

This mirrors the approach used by tracing-opentelemetry for similar thread-local guard management.

Async Behavior

When used with Instrument, the layer creates and reverts a scope around each poll of the future. Mapped field values and span info are re-applied on each enter, so reads via force_thread_local() will see the correct values during each poll. However, mutations made inside a span do not persist across .await points — each poll gets a fresh scope.

For full async context propagation across .await, use dcontext::with_context() or dcontext::ContextFuture directly.

Structs

DcontextLayer

A tracing_subscriber::Layer that automatically creates dcontext scopes when tracing spans are entered.

DcontextLayerBuilder

Builder for configuring a DcontextLayer.

SpanInfo

Span metadata exposed as a dcontext value.

Constants

SPAN_INFO_KEY

The dcontext key used for SpanInfo.

Traits

FromFieldValue

Trait for types that can be constructed from tracing field values.