What problem does it solve? Rust developers instrumenting services with OpenTelemetry face version mismatches between core and companion crates, unclear exporter configuration, and subtle pitfalls like dropped observable instrument handles that cause memory growth. This Skill provides version-aligned conventions and working code patterns for the opentelemetry-rust ecosystem. ## Core Features & Use Cases - Version-aligned crate guidance: Pins compatible combinations of opentelemetry, opentelemetry_sdk, opentelemetry-otlp, and lagging companion crates like opentelemetry-stdout and opentelemetry-appender-tracing. - Production telemetry patterns: Covers OTLP HTTP/gRPC exporters, batch processors, resource attributes, propagation, sampling, and graceful provider shutdown. - Starter snippet generator: A bootstrap script prints JSON with Cargo dependencies and code snippets for stdout traces, OTLP HTTP, metrics, manual spans, and observable instruments. - Use Case: When adding distributed tracing to an axum or tokio service, use this Skill to wire an OTLP exporter with correct endpoints, service.name resources, and shutdown handling without mixing incompatible crate versions. ## Quick Start Ask the agent to set up OpenTelemetry tracing for a Rust service with an OTLP HTTP exporter and graceful shutdown using the opentelemetry-rust conventions.
