Expand description
§Datadog Opentelemetry
This library powers Distributed Tracing, metrics and logging. It provides OpenTelemetry API and SDK compatibility with Datadog-specific features and optimizations.
§Usage
The datadog-opentelemetry crate provides an easy to use override for the rust
opentelemetry-sdk.
§Installation
Add to you Cargo.toml
datadog-opentelemetry = { version = "0.3.0" }§Creating traces, metrics and logs
§Tracing
To trace functions, you can either use the opentelemetry crate’s API or the tracing crate API with the tracing-opentelemetry bridge.
§Metrics
To collect metrics, use the opentelemetry crate’s Metrics API.
For more details, see the Datadog OpenTelemetry Rust documentation.
§Logging
- Enable with the
logsfeature of this crate
To collect logs, you can use the log crate with the opentelemetry_appender_log.
For more details, see the Datadog OpenTelemetry Rust documentation.
§Library initialization
The following examples will read datadog and opentelemetry configuration from environment variables and other available sources, initialize and set up the global providers for tracing, logging or metrics
§Tracing API
Requires
use opentelemetry::trace::TracerProvider;
use std::time::Duration;
use tracing_subscriber::{layer::SubscriberExt, util::SubscriberInitExt};
// This picks up env var configuration and other datadog configuration sources
let tracer_provider = datadog_opentelemetry::tracing().init();
tracing_subscriber::registry()
.with(
tracing_opentelemetry::layer()
.with_tracer(tracer_provider.tracer("my_application_name")),
)
.init();
tracer_provider
.shutdown_with_timeout(Duration::from_secs(1))
.expect("tracer shutdown error");§Opentelemetry trace API
Requires
opentelemetrywith thetracefeature enabled
use std::time::Duration;
// This picks up env var configuration and other datadog configuration sources
let tracer_provider = datadog_opentelemetry::tracing().init();
// Your code
// Now use standard OpenTelemetry APIs
use opentelemetry::global;
use opentelemetry::trace::Tracer;
let tracer = global::tracer("my-service");
let span = tracer.start("my-operation");
// ... do work ...
// Shutdown the tracer to flush the remaining data
tracer_provider
.shutdown_with_timeout(Duration::from_secs(1))
.expect("tracer shutdown error");§Opentelemetry metrics API
Requires
- the
metricsfeature of this crate to be enabled opentelemetrywith themetricsfeature enabledtokio
The metrics provider MUST be initialized within a tokio context
// Initialize metrics with default configuration
let meter_provider = datadog_opentelemetry::metrics().init();
// Use standard OpenTelemetry Metrics APIs
use opentelemetry::global;
use opentelemetry::metrics::Counter;
use opentelemetry::KeyValue;
let meter = global::meter("my-service");
let counter: Counter<u64> = meter.u64_counter("requests").build();
counter.add(1, &[KeyValue::new("method", "GET")]);
// Before ending the program shutdown to flush remaining metrics
meter_provider.shutdown().unwrap();§Log API
Requires
- the
logsfeature of this crate to be enabled logopentelemetry-appender-logtokio
The logger provider MUST be initialized within a tokio context
// Initialize logs with default configuration
let logger_provider = datadog_opentelemetry::logs().init();
let otel_log_appender =
opentelemetry_appender_log::OpenTelemetryLogBridge::new(&logger_provider);
log::set_boxed_logger(Box::new(otel_log_appender)).unwrap();
// Before ending the program shutdown to flush remaining logs to the collector
logger_provider.shutdown();For more details, see the Datadog OpenTelemetry Rust documentation.
§Configuration
Configuration can be passed either:
- Programmatically
use datadog_opentelemetry::configuration::Config;
let config = Config::builder()
.set_service("my_service".to_string())
.set_env("prod".to_string())
.build();
let tracer_provider = datadog_opentelemetry::tracing()
.with_config(config.clone())
// this also accepts options for the Opentelemetry SDK builder
.with_max_attributes_per_span(64)
.init();
let metrics_provider = datadog_opentelemetry::metrics()
.with_config(config.clone())
.init();
let logging_provider = datadog_opentelemetry::logs()
.with_config(config.clone())
.init();For advanced usage and configuration information, check out DatadogTracingBuilder and
configuration::ConfigBuilder
- Through env variables
DD_SERVICE=my_service DD_ENV=prod cargo runConfiguration of the OpenTelemetry SDK TracerProviderBuilder can be done when initializing the library
// Custom otel tracer sdk options
datadog_opentelemetry::tracing()
.with_max_attributes_per_span(64)
// Custom span processor
.with_span_processor(MySpanProcessor)
.init();§Support
-
MSRV: 1.84
-
opentelemetryversion: 0.31 -
tracing-opentelemetryversion: 0.32 -
opentelemetry-appender-logversion 0.31 -
logversion 0.4
§Features
metricsenabled the metrics providermetrics-grpcenabled the metrics provider, with GRPC OTLP exportmetrics-httpenabled the metrics provider, with HTTP OTLP exportlogsenabled the log providerlogs-grpcenabled the log provider, with GRPC OTLP exportlogs-httpenabled the log provider, with HTTP OTLP export
Modules§
- configuration
- Configuration for the Datadog tracing setup
- log
- Logging level
Structs§
- Datadog
Logs Builder logs - Builder for Datadog Logs with OTLP transport
- Datadog
Metrics Builder metrics - Builder for Datadog Metrics with OTLP transport
- Datadog
Tracing Builder - Builder for configuring and initializing Datadog tracing with OpenTelemetry.