​

CrateStack Telemetry

​

Status

​

Current Coverage

1. generated procedure authorization and invocation wrappers
2. generated Axum procedure routes
3. generated Axum model list routes, including @@paged list responses

1. generated model detail routes
2. generated model create, update, or delete routes
3. metrics export, OpenTelemetry export, or a dedicated telemetry abstraction layer

​

Host Setup

use tracing_subscriber::{fmt, EnvFilter};

pub fn init_telemetry() {
    let _ = fmt()
        .with_env_filter(
            EnvFilter::try_from_default_env()
                .unwrap_or_else(|_| EnvFilter::new("cratestack=info")),
        )
        .try_init();
}

​

Generated Procedure Telemetry

1. debug on successful authorize(...)
2. warn on failed authorize(...)
3. debug on successful authorize_with_db(...)
4. info / warn on invoke(...) completion or failure
5. info / warn on invoke_with_db(...) completion or failure

1. an info_span! named cratestack_procedure_route
2. warn events for transport preflight, auth, or decode failures
3. info / warn on route completion or failure

1. cratestack_procedure_invoke
2. cratestack_procedure_invoke_with_db

​

Generated Model List Telemetry

1. an info_span! named cratestack_model_list_route
2. warn events for response negotiation failures
3. warn events for auth failures
4. warn events for query parsing or selection validation failures
5. warn events when limit or offset are negative
6. info / warn on list completion or failure

​

Event Fields

​

Current Boundaries

1. it is generated directly with tracing macros instead of a framework-specific telemetry trait
2. it focuses on route, authorization, and list/procedure execution visibility rather than metrics or distributed tracing
3. it documents the current implemented behavior only, not a future observability roadmap