otel-rust

OpenTelemetry traces not exporting from Rust Tokio services often result from missing shutdown flush calls or orphaned spans. This Skill audits tracing-opentelemetry bridge setup and runtime lifecycle to ensure signals correctly export and correlate.

Broken or disconnected OpenTelemetry spans in Rust async frameworks usually stem from Tokio runtime incompatibility and dropped providers. This Skill repairs instrumentation by applying version-aware guidance for Axum, Actix-web, tonic, and rdkafka.

Setting up tracing and metrics together in Rust requires the recommended tracing and tracing-opentelemetry bridge. This Skill provides Rust-native recipes to configure SDK setup so spans, metrics, logs, and resource attributes correlate correctly.

OpenTelemetry instrumentation works with Rust gRPC via tonic and Kafka via rdkafka. This Skill covers async messaging patterns including span Links for Kafka, AMQP, and SQS to ensure traces correlate across messaging boundaries.

Safely modifying Rust source code to add OpenTelemetry requires a mutation gate that shows a proposed diff first. This Skill requests explicit user confirmation before applying any source changes, preventing unintended breaks to async services.

The best way to audit missing OpenTelemetry signals in a Rust application is an instrumentation audit checking provider lifecycle and resource attributes. This Skill troubleshoots missing traces, metrics, and logs for confirmed Rust async Tokio services.