This crate contains the OpenTelemetry Exporter implementation for OTLP.
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.
This crate provides an OTLP
(OpenTelemetry
Protocol)
exporter that sends telemetry to any OTLP-compatible backend such as the
OpenTelemetry Collector
or vendor endpoints. Exporters are provided for all three signals - Logs,
Metrics and Traces - and support both grpc and http (binary protobuf or
JSON) transports.
OTLP is the recommended way to export telemetry from OpenTelemetry, as it is vendor-neutral and supported by most observability backends.
This crate exports telemetry produced via the OpenTelemetry SDK. It is commonly used alongside:
- opentelemetry: The core OpenTelemetry API.
- opentelemetry-sdk: The OpenTelemetry SDK implementation that this exporter plugs into.
- opentelemetry-http: HTTP client abstractions used by the HTTP transport in this crate.
- opentelemetry-proto: Generated protobuf types used on the wire.
See docs.
You can find the release notes (changelog) here.
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.