Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

README.md

OpenTelemetry Proto

OpenTelemetry — An observability framework for cloud-native software.

This crate contains generated files from opentelemetry-proto repository and transformations between types from generated files and types defined in opentelemetry.

Crates.io: opentelemetry-proto 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.

Supported Rust Versions

What does this crate contain?

This crate provides auto-generated Protobuf types from the OpenTelemetry protocol specification, along with conversion implementations between these generated types and the types defined in the opentelemetry crate. It is used internally by exporters such as opentelemetry-otlp to serialize and deserialize telemetry data.

Getting started

See docs.

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.