tracing is a framework for instrumenting Rust programs to collect
structured, event-based diagnostic information. This crate provides a
subscriber that connects spans from multiple systems into a trace and
emits them to OpenTelemetry-compatible distributed tracing systems
for processing and visualization.
The crate provides the following types:
OpenTelemetryLayeradds OpenTelemetry context to all
OpenTelemetrySpanExtallows OpenTelemetry parent trace information to be injected and extracted from a
Compiler support: requires
use stdout; use ; use SubscriberExt; use Registry;
# Run a supported collector like jaeger in the background $ docker run -d -p6831:6831/udp -p6832:6832/udp -p16686:16686 jaegertracing/all-in-one:latest # Run example to produce spans (from parent examples directory) $ cargo run --example opentelemetry # View spans (see the image below) $ firefox http://localhost:16686/
metrics: Enables the [
MetricsSubscriber] type, a [subscriber] that exports OpenTelemetry metrics from specifically-named events. This enables the
metricsfeature flag on the
Supported Rust Versions
Tracing Opentelemetry is built against the latest stable release. The minimum supported version is 1.56. The current Tracing version is not guaranteed to build on Rust versions earlier than the minimum supported version.
Tracing follows the same compiler support policies as the rest of the Tokio project. The current stable Rust compiler and the three most recent minor versions before it will always be supported. For example, if the current stable compiler version is 1.45, the minimum supported version will not be increased past 1.42, three minor versions prior. Increasing the minimum supported compiler version is not considered a semver breaking change as long as doing so complies with this policy.
This project is licensed under the MIT license.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tracing by you, shall be licensed as MIT, without any additional terms or conditions.