Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
OpenTelemetry Collector Rust Exporter
OTLP
integration for applications instrumented with OpenTelemetry
.
Overview
OpenTelemetry
is a collection of tools, APIs, and SDKs used to instrument,
generate, collect, and export telemetry data (metrics, logs, and traces) for
analysis in order to understand your software's performance and behavior.
This crate provides an exporter for sending trace and metric data in the OTLP format to the OpenTelemetry collector. 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.
Quickstart
First make sure you have a running version of the opentelemetry collector you want to send data to:
$ docker run -p 55680:55680 otel/opentelemetry-collector-dev:latest
Then install a new pipeline with the recommended defaults to start exporting telemetry:
use tracer;
Performance
For optimal performance, a batch exporter is recommended as the simple
exporter will export each span synchronously on drop. You can enable the
tokio
or async-std
features to have a batch exporter configured for
you automatically for either executor when you install the pipeline.
[]
= { = "*", = ["tokio"] }
= "*"
Kitchen Sink Full Configuration
Example showing how to override all configuration options. See the
OtlpPipelineBuilder
docs for details of each option.
use ;
use ;
use ;
use Duration;