otlp-logger

OpenTelemetry Logging with Tokio Tracing

This crate provides a convienent way to initialize the OpenTelemetry logger with otlp endpoint. It uses the opentelemetry and tracing crates to provide structured, context-aware logging for Rust applications.

Simply add the following to your Cargo.toml:

[dependencies]
tracing = "0.1"
otlp-logger = "0.1"

In your code initialize the logger with:

fn main() {
   otlp_logger::init();
  // Your application code
}

If the OTEL_EXPORTER_OTLP_ENDPOINT environment variable is set, the OpenTelemetry logger will be used. Otherwise, the logger will default to stdout.

The OpenTelemetry logger can be configured with the following environment variables:

• OTEL_EXPORTER_OTLP_ENDPOINT: The endpoint to send OTLP data to.
• OTEL_SERVICE_NAME: The name of the service.
• OTEL_SERVICE_NAMESPACE: The namespace of the service.
• OTEL_SERVICE_VERSION: The version of the service.
• OTEL_SERVICE_INSTANCE_ID: The instance ID of the service.
• OTEL_DEPLOYMENT_ENVIRONMENT: The deployment environment of the service.

The OpenTelemetry logger can also be configured with the OtlpConfig struct, which can be passed to the init_with_config function. The OtlpConfig struct can be built with the OtlpConfigBuilder struct.

Once the logger is initialized, you can use the tracing macros to log messages. For example:

use tracing::{info, error};

fn main() {
   otlp_logger::init();
   info!("This is an info message");
   error!("This is an error message");
}

Both traces and metrics are sent to the configured OTLP endpoint. The traces filter level can be controled with RUST_LOG environment variable. The metrics filter level is fixed at LevelFilter::TRACE so as not to pollute the logs with meter increments and the like when at DEBUG or higher levels.

License: Apache-2.0