Skip to content

Commit 97c0f2d

Browse files
committed
more cleanups
1 parent c2c1d0a commit 97c0f2d

File tree

1 file changed

+13
-49
lines changed

1 file changed

+13
-49
lines changed

opentelemetry/src/lib.rs

+13-49
Original file line numberDiff line numberDiff line change
@@ -116,74 +116,38 @@
116116
//!
117117
//! In addition to `opentelemetry`, the [`open-telemetry/opentelemetry-rust`]
118118
//! repository contains several additional crates designed to be used with the
119-
//! `opentelemetry` ecosystem. This includes a collection of trace
120-
//! `SpanExporter` and metrics pull and push controller implementations, as well
121-
//! as utility and adapter crates to assist in propagating state and
119+
//! `opentelemetry` ecosystem. This includes exporters, samplers, as well as
120+
//! utility and adapter crates to assist in propagating context and
122121
//! instrumenting applications.
123122
//!
124123
//! In particular, the following crates are likely to be of interest:
125124
//!
126-
//! - [`opentelemetry_sdk`] provides the SDK used to configure providers.
125+
//! - [`opentelemetry_sdk`] provides the OpenTelemetry SDK used to configure providers.
127126
//! - [`opentelemetry-http`] provides an interface for injecting and extracting
128127
//! trace information from [`http`] headers.
129-
//! - [`opentelemetry-jaeger`] provides a pipeline and exporter for sending
130-
//! trace information to [`Jaeger`].
131-
//! - [`opentelemetry-otlp`] exporter for sending trace and metric data in the
132-
//! OTLP format to the OpenTelemetry collector.
128+
//! - [`opentelemetry-otlp`] exporter for sending telemetry in the
129+
//! OTLP format.
133130
//! - [`opentelemetry-prometheus`] provides a pipeline and exporter for sending
134131
//! metrics information to [`Prometheus`].
135132
//! - [`opentelemetry-zipkin`] provides a pipeline and exporter for sending
136133
//! trace information to [`Zipkin`].
137-
//! - [`opentelemetry-datadog`] provides additional exporters to [`Datadog`].
138-
//! - [`opentelemetry-aws`] provides unofficial propagators for AWS X-ray.
139-
//! - [`opentelemetry-contrib`] provides additional exporters and propagators that are
140-
//! experimental.
141-
//! - [`opentelemetry-semantic-conventions`] provides standard names and
142-
//! semantic otel conventions.
143-
//! - [`opentelemetry-stackdriver`] provides an exporter for Google's [Cloud Trace]
144-
//! (which used to be called StackDriver).
145-
//!
146-
//! Additionally, there are also several third-party crates which are not
147-
//! maintained by the `opentelemetry` project. These include:
148-
//!
149-
//! - [`tracing-opentelemetry`] provides integration for applications
150-
//! instrumented using the [`tracing`] API and ecosystem.
151-
//! - [`actix-web-opentelemetry`] provides integration for the [`actix-web`] web
152-
//! server and ecosystem.
153-
//! - [`opentelemetry-application-insights`] provides an unofficial [Azure
154-
//! Application Insights] exporter.
155-
//! - [`opentelemetry-tide`] provides integration for the [`Tide`] web server
156-
//! and ecosystem.
157-
//!
158-
//! If you're the maintainer of an `opentelemetry` ecosystem crate not listed
159-
//! above, please let us know! We'd love to add your project to the list!
160-
//!
161-
//! [`actix-web-opentelemetry`]: https://crates.io/crates/actix-web-opentelemetry
162-
//! [`actix-web`]: https://crates.io/crates/actix-web
163-
//! [`Datadog`]: https://www.datadoghq.com
134+
//!
135+
//! In addition, there are several other useful crates in the [OTel Rust
136+
//! Contrib
137+
//! repo](https://github.com/open-telemetry/opentelemetry-rust-contrib). A lot
138+
//! of crates maintained outside OpenTelemetry owned repos can be found in the
139+
//! [OpenTelemetry
140+
//! Registry](https://opentelemetry.io/ecosystem/registry/?language=rust).
141+
//!
164142
//! [`http`]: https://crates.io/crates/http
165-
//! [`Jaeger`]: https://www.jaegertracing.io
166143
//! [`open-telemetry/opentelemetry-rust`]: https://github.com/open-telemetry/opentelemetry-rust
167144
//! [`opentelemetry_sdk`]: https://crates.io/crates/opentelemetry_sdk
168-
//! [`opentelemetry-application-insights`]: https://crates.io/crates/opentelemetry-application-insights
169-
//! [`opentelemetry-aws`]: https://crates.io/crates/opentelemetry-aws
170-
//! [`opentelemetry-contrib`]: https://crates.io/crates/opentelemetry-contrib
171-
//! [`opentelemetry-datadog`]: https://crates.io/crates/opentelemetry-datadog
172145
//! [`opentelemetry-http`]: https://crates.io/crates/opentelemetry-http
173-
//! [`opentelemetry-jaeger`]: https://crates.io/crates/opentelemetry-jaeger
174146
//! [`opentelemetry-otlp`]: https://crates.io/crates/opentelemetry-otlp
175147
//! [`opentelemetry-prometheus`]: https://crates.io/crates/opentelemetry-prometheus
176-
//! [`opentelemetry-semantic-conventions`]: https://crates.io/crates/opentelemetry-semantic-conventions
177-
//! [`opentelemetry-stackdriver`]: https://crates.io/crates/opentelemetry-stackdriver
178-
//! [`opentelemetry-tide`]: https://crates.io/crates/opentelemetry-tide
179148
//! [`opentelemetry-zipkin`]: https://crates.io/crates/opentelemetry-zipkin
180149
//! [`Prometheus`]: https://prometheus.io
181-
//! [`Tide`]: https://crates.io/crates/tide
182-
//! [`tracing-opentelemetry`]: https://crates.io/crates/tracing-opentelemetry
183-
//! [`tracing`]: https://crates.io/crates/tracing
184150
//! [`Zipkin`]: https://zipkin.io
185-
//! [Azure Application Insights]: https://docs.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview
186-
//! [Cloud Trace]: https://cloud.google.com/trace/
187151
//!
188152
//! ## Supported Rust Versions
189153
//!

0 commit comments

Comments
 (0)