opentelemetry-jaeger-propagator
| Crates.io | opentelemetry-jaeger-propagator |
| lib.rs | opentelemetry-jaeger-propagator |
| version | 0.28.0 |
| source | src |
| created_at | 2024-02-25 04:28:47.998848 |
| updated_at | 2025-02-10 18:25:23.117899 |
| description | Jaeger propagator for OpenTelemetry |
| homepage | https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-jaeger-propagator |
| repository | https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-jaeger-propagator |
| max_upload_size | |
| id | 1152178 |
| size | 48,165 |
rust-publishers (github:open-telemetry:rust-publishers)
documentation
README
OpenTelemetry Jaeger Propagator
This crate contains [Jaeger] propagator integration for applications
instrumented with [OpenTelemetry]. To export telemetry to Jaeger, use the
opentelemetry-otlp crate.
OpenTelemetry Overview
OpenTelemetry is an Observability framework and toolkit designed to create and manage telemetry data such as traces, metrics, and logs. OpenTelemetry is vendor- and tool-agnostic, meaning that it can be used with a broad variety of Observability backends, including open source tools like [Jaeger] and [Prometheus], as well as commercial offerings.
OpenTelemetry is not an observability backend like Jaeger, Prometheus, or other commercial vendors. OpenTelemetry is focused on the generation, collection, management, and export of telemetry. A major goal of OpenTelemetry is that you can easily instrument your applications or systems, no matter their language, infrastructure, or runtime environment. Crucially, the storage and visualization of telemetry is intentionally left to other tools.
Release Notes
You can find the release notes (changelog) here.
Supported Rust Versions
OpenTelemetry is built against the latest stable release. The minimum supported version is 1.75.0. The current OpenTelemetry version is not guaranteed to build on Rust versions earlier than the minimum supported version.
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.49, the minimum supported version will not be increased past 1.46, 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.