1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386
//! The OTLP Exporter supports exporting trace and metric data in the OTLP
//! format to the OpenTelemetry collector or other compatible backend.
//!
//! The OpenTelemetry Collector offers a vendor-agnostic implementation on how
//! to receive, process, and export telemetry data. In addition, it removes
//! the need to run, operate, and maintain multiple agents/collectors in
//! order to support open-source telemetry data formats (e.g. Jaeger,
//! Prometheus, etc.) sending to multiple open-source or commercial back-ends.
//!
//! Currently, this crate only support sending tracing data or metrics in OTLP
//! via grpc and http(in binary format). Supports for other format and protocol
//! will be added in the future. The details of what's currently offering in this
//! crate can be found in this doc.
//!
//! # Quickstart
//!
//! First make sure you have a running version of the opentelemetry collector
//! you want to send data to:
//!
//! ```shell
//! $ docker run -p 4317:4317 otel/opentelemetry-collector-dev:latest
//! ```
//!
//! Then install a new pipeline with the recommended defaults to start exporting
//! telemetry. You will have to build a OTLP exporter first.
//!
//! Tracing and metrics pipelines can be started with `new_pipeline().tracing()` and
//! `new_pipeline().metrics()` respectively.
//!
//! ```no_run
//! use opentelemetry::trace::Tracer;
//!
//! fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync + 'static>> {
//! // First, create a OTLP exporter builder. Configure it as you need.
//! let otlp_exporter = opentelemetry_otlp::new_exporter().tonic();
//! // Then pass it into pipeline builder
//! let tracer = opentelemetry_otlp::new_pipeline()
//! .tracing()
//! .with_exporter(otlp_exporter)
//! .install_simple()?;
//!
//! tracer.in_span("doing_work", |cx| {
//! // Traced app logic here...
//! });
//!
//! Ok(())
//! }
//! ```
//!
//! ## Performance
//!
//! For optimal performance, a batch exporter is recommended as the simple
//! exporter will export each span synchronously on dropping. You can enable the
//! [`rt-tokio`], [`rt-tokio-current-thread`] or [`rt-async-std`] features and
//! specify a runtime on the pipeline builder to have a batch exporter
//! configured for you automatically.
//!
//! ```toml
//! [dependencies]
//! opentelemetry = { version = "*", features = ["async-std"] }
//! opentelemetry-otlp = { version = "*", features = ["grpc-sys"] }
//! ```
//!
//! ```no_run
//! # fn main() -> Result<(), opentelemetry::trace::TraceError> {
//! let tracer = opentelemetry_otlp::new_pipeline()
//! .tracing()
//! .with_exporter(opentelemetry_otlp::new_exporter().tonic())
//! .install_batch(opentelemetry::runtime::AsyncStd)?;
//! # Ok(())
//! # }
//! ```
//!
//! [`tokio`]: https://tokio.rs
//! [`async-std`]: https://async.rs
//!
//! # Kitchen Sink Full Configuration
//!
//! Example showing how to override all configuration options.
//!
//! Generally there are two parts of configuration. One is metrics config
//! or tracing config. Users can config it via [`OtlpTracePipeline`]
//! or [`OtlpMetricPipeline`]. The other is exporting configuration.
//! Users can set those configurations using [`OtlpExporterPipeline`] based
//! on the choice of exporters.
//!
//! ```no_run
//! use opentelemetry::{KeyValue, trace::Tracer};
//! use opentelemetry::sdk::{trace::{self, RandomIdGenerator, Sampler}, Resource};
//! use opentelemetry::sdk::metrics::{selectors, PushController};
//! use opentelemetry::sdk::util::tokio_interval_stream;
//! use opentelemetry_otlp::{Protocol, WithExportConfig, ExportConfig};
//! use std::time::Duration;
//! use tonic::metadata::*;
//!
//! fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync + 'static>> {
//! let mut map = MetadataMap::with_capacity(3);
//!
//! map.insert("x-host", "example.com".parse().unwrap());
//! map.insert("x-number", "123".parse().unwrap());
//! map.insert_bin("trace-proto-bin", MetadataValue::from_bytes(b"[binary data]"));
//!
//! let tracer = opentelemetry_otlp::new_pipeline()
//! .tracing()
//! .with_exporter(
//! opentelemetry_otlp::new_exporter()
//! .tonic()
//! .with_endpoint("http://localhost:4317")
//! .with_timeout(Duration::from_secs(3))
//! .with_metadata(map)
//! )
//! .with_trace_config(
//! trace::config()
//! .with_sampler(Sampler::AlwaysOn)
//! .with_id_generator(RandomIdGenerator::default())
//! .with_max_events_per_span(64)
//! .with_max_attributes_per_span(16)
//! .with_max_events_per_span(16)
//! .with_resource(Resource::new(vec![KeyValue::new("service.name", "example")])),
//! )
//! .install_batch(opentelemetry::runtime::Tokio)?;
//!
//! let export_config = ExportConfig {
//! endpoint: "http://localhost:4317".to_string(),
//! timeout: Duration::from_secs(3),
//! protocol: Protocol::Grpc
//! };
//!
//! let meter = opentelemetry_otlp::new_pipeline()
//! .metrics(tokio::spawn, tokio_interval_stream)
//! .with_exporter(
//! opentelemetry_otlp::new_exporter()
//! .tonic()
//! .with_export_config(export_config),
//! // can also config it using with_* functions like the tracing part above.
//! )
//! .with_stateful(true)
//! .with_period(Duration::from_secs(3))
//! .with_timeout(Duration::from_secs(10))
//! .with_aggregator_selector(selectors::simple::Selector::Exact)
//! .build();
//!
//! tracer.in_span("doing_work", |cx| {
//! // Traced app logic here...
//! });
//!
//! Ok(())
//! }
//! ```
//!
//! # Grpc libraries comparison
//!
//! The table below provides a short comparison between `grpcio` and `tonic`, two
//! of the most popular grpc libraries in Rust. Users can choose between them when
//! working with otlp and grpc.
//!
//! | Project | [hyperium/tonic](https://github.com/hyperium/tonic) | [tikv/grpc-rs](https://github.com/tikv/grpc-rs) |
//! |---|---|---|
//! | Feature name | --features=default | --features=grpc-sys |
//! | gRPC library | [`tonic`](https://crates.io/crates/tonic) | [`grpcio`](https://crates.io/crates/grpcio) |
//! | Transport | [hyperium/hyper](https://github.com/hyperium/hyper) (Rust) | [grpc/grpc](https://github.com/grpc/grpc) (C++ binding) |
//! | TLS support | yes | yes |
//! | TLS optional | yes | yes |
//! | TLS library | rustls | OpenSSL |
//! | Supported .proto generator | [`prost`](https://crates.io/crates/prost) | [`prost`](https://crates.io/crates/prost), [`protobuf`](https://crates.io/crates/protobuf) |
#![warn(
future_incompatible,
missing_debug_implementations,
missing_docs,
nonstandard_style,
rust_2018_idioms,
unreachable_pub,
unused
)]
#![allow(elided_lifetimes_in_paths)]
#![cfg_attr(
docsrs,
feature(doc_cfg, doc_auto_cfg),
deny(rustdoc::broken_intra_doc_links)
)]
#![cfg_attr(test, deny(warnings))]
mod exporter;
#[cfg(feature = "metrics")]
mod metric;
#[cfg(feature = "trace")]
mod span;
mod transform;
pub use crate::exporter::ExportConfig;
#[cfg(feature = "trace")]
pub use crate::span::{
OtlpTracePipeline, SpanExporter, SpanExporterBuilder, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT,
OTEL_EXPORTER_OTLP_TRACES_TIMEOUT,
};
#[cfg(feature = "metrics")]
pub use crate::metric::{
MetricsExporter, OtlpMetricPipeline, OTEL_EXPORTER_OTLP_METRICS_ENDPOINT,
OTEL_EXPORTER_OTLP_METRICS_TIMEOUT,
};
pub use crate::exporter::{
HasExportConfig, WithExportConfig, OTEL_EXPORTER_OTLP_ENDPOINT,
OTEL_EXPORTER_OTLP_ENDPOINT_DEFAULT, OTEL_EXPORTER_OTLP_TIMEOUT,
OTEL_EXPORTER_OTLP_TIMEOUT_DEFAULT,
};
use opentelemetry::sdk::export::ExportError;
#[cfg(feature = "metrics")]
use std::time::{Duration, SystemTime, UNIX_EPOCH};
#[cfg(feature = "grpc-sys")]
pub use crate::exporter::grpcio::{Compression, Credentials, GrpcioExporterBuilder};
#[cfg(feature = "http-proto")]
pub use crate::exporter::http::HttpExporterBuilder;
#[cfg(feature = "grpc-tonic")]
pub use crate::exporter::tonic::TonicExporterBuilder;
#[cfg(feature = "serialize")]
use serde::{Deserialize, Serialize};
/// General builder for both tracing and metrics.
#[derive(Debug)]
pub struct OtlpPipeline;
/// Build a OTLP metrics or tracing exporter builder. See functions below to understand
/// what's currently supported.
#[derive(Debug)]
pub struct OtlpExporterPipeline;
impl OtlpExporterPipeline {
/// Use tonic as grpc layer, return a `TonicExporterBuilder` to config tonic and build the exporter.
///
/// This exporter can be used in both `tracing` and `metrics` pipeline.
#[cfg(feature = "grpc-tonic")]
pub fn tonic(self) -> TonicExporterBuilder {
TonicExporterBuilder::default()
}
/// Use grpcio as grpc layer, return a `GrpcioExporterBuilder` to config the grpcio and build the exporter.
///
/// This exporter can only be used in `tracing` pipeline. Support for `metrics` pipeline will be
/// added in the future.
#[cfg(feature = "grpc-sys")]
pub fn grpcio(self) -> GrpcioExporterBuilder {
GrpcioExporterBuilder::default()
}
/// Use HTTP as transport layer, return a `HttpExporterBuilder` to config the http transport
/// and build the exporter.
///
/// This exporter can only be used in `tracing` pipeline. Support for `metrics` pipeline will be
/// added in the future.
#[cfg(feature = "http-proto")]
pub fn http(self) -> HttpExporterBuilder {
HttpExporterBuilder::default()
}
}
/// Create a new pipeline builder with the recommended configuration.
///
/// ## Examples
///
/// ```no_run
/// fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync + 'static>> {
/// let tracing_builder = opentelemetry_otlp::new_pipeline()
/// .tracing();
///
/// Ok(())
/// }
/// ```
pub fn new_pipeline() -> OtlpPipeline {
OtlpPipeline
}
/// Create a builder to build OTLP metrics exporter or tracing exporter.
pub fn new_exporter() -> OtlpExporterPipeline {
OtlpExporterPipeline
}
/// Wrap type for errors from this crate.
#[derive(thiserror::Error, Debug)]
pub enum Error {
/// Wrap error from [`tonic::transport::Error`]
#[cfg(feature = "grpc-tonic")]
#[error("transport error {0}")]
Transport(#[from] tonic::transport::Error),
/// Wrap the [`tonic::codegen::http::uri::InvalidUri`] error
#[cfg(any(feature = "grpc-tonic", feature = "http-proto"))]
#[error("invalid URI {0}")]
InvalidUri(#[from] http::uri::InvalidUri),
/// Wrap type for [`tonic::Status`]
#[cfg(feature = "grpc-tonic")]
#[error("the grpc server returns error ({code}): {message}")]
Status {
/// grpc status code
code: tonic::Code,
/// error message
message: String,
},
/// Wrap errors from grpcio.
#[cfg(feature = "grpc-sys")]
#[error("grpcio error {0}")]
Grpcio(#[from] grpcio::Error),
/// Http requests failed because no http client is provided.
#[cfg(feature = "http-proto")]
#[error(
"no http client, you must select one from features or provide your own implementation"
)]
NoHttpClient,
/// Http requests failed.
#[cfg(feature = "http-proto")]
#[error("http request failed with {0}")]
RequestFailed(#[from] http::Error),
/// The provided value is invalid in HTTP headers.
#[cfg(feature = "http-proto")]
#[error("http header value error {0}")]
InvalidHeaderValue(#[from] http::header::InvalidHeaderValue),
/// The provided name is invalid in HTTP headers.
#[cfg(feature = "http-proto")]
#[error("http header name error {0}")]
InvalidHeaderName(#[from] http::header::InvalidHeaderName),
/// Prost encode failed
#[cfg(feature = "http-proto")]
#[error("prost encoding error {0}")]
EncodeError(#[from] prost::EncodeError),
/// The lock in exporters has been poisoned.
#[cfg(feature = "metrics")]
#[error("the lock of the {0} has been poisoned")]
PoisonedLock(&'static str),
/// The pipeline will need a exporter to complete setup. Throw this error if none is provided.
#[error("no exporter builder is provided, please provide one using with_exporter() method")]
NoExporterBuilder,
}
#[cfg(feature = "grpc-tonic")]
impl From<tonic::Status> for Error {
fn from(status: tonic::Status) -> Error {
Error::Status {
code: status.code(),
message: {
if !status.message().is_empty() {
", detailed error message: ".to_string() + status.message()
} else {
"".to_string()
}
},
}
}
}
impl ExportError for Error {
fn exporter_name(&self) -> &'static str {
"otlp"
}
}
/// The communication protocol to use when exporting data.
#[cfg_attr(feature = "serialize", derive(Deserialize, Serialize))]
#[derive(Clone, Copy, Debug)]
pub enum Protocol {
/// GRPC protocol
Grpc,
// TODO add support for other protocols
// HttpJson,
/// HTTP protocol with binary protobuf
HttpBinary,
}
#[cfg(feature = "metrics")]
pub(crate) fn to_nanos(time: SystemTime) -> u64 {
time.duration_since(UNIX_EPOCH)
.unwrap_or_else(|_| Duration::from_secs(0))
.as_nanos() as u64
}