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
- Add deprecation flags to the various components to give notices in
users compilers.
- Add more definition around the deprecation in the README.
- Add a deprecation badge for crates.io.
- Update changelog to show deprecation notice.
Relates #995
Copy file name to clipboardexpand all lines: opentelemetry-jaeger/CHANGELOG.md
+11-4
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,23 @@
1
1
# Changelog
2
2
3
+
## Deprecation Notice
4
+
5
+
Starting with [Jaeger v1.38](https://github.com/jaegertracing/jaeger/releases/tag/v1.38.0) Jaeger supports the OpenTelemetry Protocol (OTLP).
6
+
[OpenTelemetry has recommended](https://opentelemetry.io/blog/2022/jaeger-native-otlp/) migrating to OTLP.
7
+
8
+
Please check the [README](https://crates.io/crates/opentelemetry-jaeger) for more information.
9
+
3
10
## vNext
4
11
5
12
### Changed
6
13
7
-
-**Breaking** Remove support for surf HTTP client [#1537](https://github.com/open-telemetry/opentelemetry-rust/pull/1537)
8
14
- Update to tonic 0.11 and prost 0.12 (#1536)
9
15
10
-
##v0.21.0
16
+
### Removed
11
17
12
-
### Changed
13
-
- Previously, the opentelemetry-jaeger crate exposed both a Jaeger exporter and a Jaeger propagator. Going forwards, the Jaeger propagator functionality has been moved to a new crate [opentelemetry-jaeger-propagator](../opentelemetry-jaeger-propagator/) to prepare for opentelemetry-jaeger exporter deprecation. Starting with [Jaeger v1.35](https://github.com/jaegertracing/jaeger/releases/tag/v1.35.0), Jaeger supports the OpenTelemetry Protocol (OTLP). [OpenTelemetry has recommended](https://opentelemetry.io/blog/2022/jaeger-native-otlp/) that Jaeger exporters be deprecated from OpenTelemetry SDKs in favor of sending traces to Jaeger clients using OTLP. An example and further discussion of how to consume OpenTelemetry spans with Jaeger can be found at [Introducing native support for OpenTelemetry in Jaeger](https://medium.com/jaegertracing/introducing-native-support-for-opentelemetry-in-jaeger-eb661be8183c).
18
+
-**Breaking** Jaeger propagator functionality has been moved to a new crate [opentelemetry-jaeger-propagator](../opentelemetry-jaeger-propagator/)
19
+
to prepare for opentelemetry-jaeger exporter deprecation. [#1487](https://github.com/open-telemetry/opentelemetry-rust/pull/1487)
20
+
-**Breaking** Remove support for surf HTTP client [#1537](https://github.com/open-telemetry/opentelemetry-rust/pull/1537)
As of [Jaeger 1.35.0], released in Sept 2022, ingesting the OpenTelemetry Protocol (OTLP) is stable and
9
+
as a result, language specific Jaeger exporters within OpenTelemetry SDKs are [recommended for deprecation by the OpenTelemetry project][jaeger-deprecation].
10
+
More information and examples of using OTLP with Jaeger can be found in [Introducing native support for OpenTelemetry in Jaeger][jaeger-otlp]
11
+
and [Exporting OTLP traces to Jaeger][exporting-otlp].
12
+
13
+
The opentelemetry-jaeger crate previously contained both a Jaeger exporter and a Jaeger propagator.
14
+
To prepare for the deprecation of the Jaeger exporter, the Jaeger propagator implementation has been migrated to
[Jaeger](https://www.jaegertracing.io/) supports the OpenTelemetry Protocol (OTLP) as of [v1.35.0](https://github.com/jaegertracing/jaeger/releases/tag/v1.35.0) and as a result, language specific Jaeger exporters within OpenTelemetry SDKs are [recommended for deprecation by the OpenTelemetry project](https://opentelemetry.io/blog/2022/jaeger-native-otlp/). More information and examples of using OTLP with Jaeger can be found in [Introducing native support for OpenTelemetry in Jaeger](https://medium.com/jaegertracing/introducing-native-support-for-opentelemetry-in-jaeger-eb661be8183c) and [Exporting OTLP traces to Jaeger](https://github.com/open-telemetry/opentelemetry-rust/tree/main/examples/tracing-jaeger).
17
-
18
-
The opentelemetry-jaeger crate previously contained both a Jaeger exporter and a Jaeger propagator. To prepare for the deprecation of the Jaeger exporter, the Jaeger propagator implementation has been migrated to [opentelemetry-jaeger-propagator](../opentelemetry-jaeger-propagator/).
19
-
20
30
## Overview
21
31
22
32
[`OpenTelemetry`] is a collection of tools, APIs, and SDKs used to instrument,
@@ -28,6 +38,11 @@ Jaeger `agent` or `collector` endpoint for processing and visualization.
#[allow(clippy::field_reassign_with_default)]// make sure when collector_cilent and wasm_collector_client are both set. We will create a wasm type client
197
+
#[allow(clippy::field_reassign_with_default)]
198
+
// make sure when collector_cilent and wasm_collector_client are both set. We will create a wasm type client
199
+
#[deprecated(
200
+
since = "0.21.0",
201
+
note = "Please Migrate to opentelemetry-otlp exporter."
0 commit comments