18 breaking releases

0.26.0 Oct 1, 2024
0.17.0 Jul 15, 2024
0.15.0 Feb 25, 2024
0.14.0 Nov 6, 2023
0.3.0 Nov 10, 2020

#144 in Debugging

Download history 335934/week @ 2024-07-18 350726/week @ 2024-07-25 322238/week @ 2024-08-01 359698/week @ 2024-08-08 359301/week @ 2024-08-15 381165/week @ 2024-08-22 355667/week @ 2024-08-29 417308/week @ 2024-09-05 392234/week @ 2024-09-12 410796/week @ 2024-09-19 430194/week @ 2024-09-26 442133/week @ 2024-10-03 442008/week @ 2024-10-10 503233/week @ 2024-10-17 502840/week @ 2024-10-24 469292/week @ 2024-10-31

2,015,280 downloads per month
Used in 308 crates (124 directly)

Apache-2.0

1.5MB
25K SLoC

OpenTelemetry OTLP Exporter

OpenTelemetry — An observability framework for cloud-native software.

This crate contains the OpenTelemetry Exporter implementation for OTLP.

Crates.io: opentelemetry-otlp Documentation LICENSE GitHub Actions CI codecov Slack

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.

Compiler support: requires rustc 1.71.1+

Getting started

See docs.

Supported Rust Versions

OpenTelemetry is built against the latest stable release. The minimum supported version is 1.71.1. 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.

Dependencies

~1–14MB
~187K SLoC