You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This crate provides a bridge for integrating the [tracing crate](https://tracing.rs/) with OpenTelemetry's logging pipeline. It includes:
41
+
42
+
-**Log Appender**: A component that captures log events from tracing and forwards them to OpenTelemetry's logging system
43
+
-**Event Bridge**: Converts tracing events into OpenTelemetry log records while preserving metadata and context
44
+
-**Integration Support**: Seamless integration with existing tracing-based applications to enable OpenTelemetry log collection
45
+
46
+
This appender is specifically designed for scenarios where you want to collect logs through OpenTelemetry while using the tracing crate for instrumentation.
47
+
48
+
## Getting started
49
+
50
+
See the [docs](https://docs.rs/opentelemetry-appender-tracing) for detailed examples and API reference.
51
+
38
52
## Release Notes
39
53
40
54
You can find the release notes (changelog) [here](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-appender-tracing/CHANGELOG.md).
This crate provides Jaeger-specific context propagation for OpenTelemetry applications. It includes:
37
+
38
+
-**Jaeger Propagator**: Implementation of Jaeger's text map propagation format for distributed tracing
39
+
-**Context Extraction**: Ability to extract Jaeger trace context from HTTP headers and other carriers
40
+
-**Context Injection**: Functionality to inject OpenTelemetry trace context into Jaeger format for downstream services
41
+
-**Legacy Compatibility**: Support for applications that need to interoperate with existing Jaeger-instrumented services
42
+
43
+
Note: This crate is specifically for context propagation. To export telemetry data to Jaeger, use the `opentelemetry-otlp` crate.
44
+
45
+
## Getting started
46
+
47
+
See the [docs](https://docs.rs/opentelemetry-jaeger-propagator) for detailed examples and API reference.
48
+
34
49
## Release Notes
35
50
36
51
You can find the release notes (changelog) [here](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-jaeger-propagator/CHANGELOG.md).
Copy file name to clipboardExpand all lines: opentelemetry-otlp/README.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,20 @@ of telemetry is intentionally left to other tools.
35
35
[Prometheus]: https://prometheus.io
36
36
[Jaeger]: https://www.jaegertracing.io
37
37
38
+
### What does this crate contain?
39
+
40
+
This crate provides OTLP (OpenTelemetry Protocol) exporter implementations for sending telemetry data to OTLP-compatible backends. It includes:
41
+
42
+
-**Trace Exporter**: Export distributed tracing data in OTLP format
43
+
-**Metrics Exporter**: Export metrics data to OTLP endpoints
44
+
-**Logs Exporter**: Export log data using the OTLP protocol
45
+
-**HTTP Transport**: Send telemetry over HTTP/1.1 and HTTP/2 with configurable compression
46
+
-**gRPC Transport**: Send telemetry using gRPC protocol for high-performance scenarios
47
+
-**Authentication Support**: Built-in support for various authentication mechanisms (headers, mTLS, etc.)
48
+
-**Batch Processing**: Efficient batching and retry mechanisms for reliable telemetry delivery
49
+
50
+
The OTLP format is the recommended way to export telemetry as it's vendor-neutral and supported by many observability backends including Jaeger, Prometheus, and commercial vendors.
**⚠️ This crate is deprecated and no longer recommended for use.**
50
+
51
+
This crate previously provided direct Prometheus metrics export functionality, but has been discontinued due to:
52
+
- Dependency on unmaintained `protobuf` crate
53
+
- Unresolved security vulnerabilities
54
+
- Limited maintenance resources
55
+
56
+
For new projects, use the [OTLP exporter](https://docs.rs/opentelemetry-otlp/) instead, as Prometheus now natively supports OTLP.
57
+
58
+
## Getting started
59
+
60
+
**For new projects:** Use the [opentelemetry-otlp](https://docs.rs/opentelemetry-otlp/) crate instead. See the [Prometheus OTLP documentation](https://prometheus.io/docs/guides/opentelemetry/#enable-the-otlp-receiver) for integration details.
61
+
62
+
**For existing projects:** See the [docs](https://docs.rs/opentelemetry-prometheus) for legacy API reference, but plan migration to OTLP.
63
+
47
64
## Release Notes
48
65
49
66
You can find the release notes (changelog) [here](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-prometheus/CHANGELOG.md).
67
+
68
+
## Supported Rust Versions
69
+
70
+
OpenTelemetry is built against the latest stable release. The minimum supported
71
+
version is 1.75.0. The current OpenTelemetry version is not guaranteed to build
72
+
on Rust versions earlier than the minimum supported version.
73
+
74
+
The current stable Rust compiler and the three most recent minor versions
75
+
before it will always be supported. For example, if the current stable compiler
76
+
version is 1.49, the minimum supported version will not be increased past 1.46,
77
+
three minor versions prior. Increasing the minimum supported compiler version
78
+
is not considered a semver breaking change as long as doing so complies with
0 commit comments