-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new opentelemetry-jaeger-propagator library #1487
Create new opentelemetry-jaeger-propagator library #1487
Conversation
|
…er-propagator/Cargo.toml
…ger-propagator module
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1487 +/- ##
=======================================
- Coverage 64.0% 63.9% -0.2%
=======================================
Files 142 144 +2
Lines 19507 20042 +535
=======================================
+ Hits 12499 12808 +309
- Misses 7008 7234 +226 ☔ View full report in Codecov by Sentry. |
…ere is a Result::Err
…try_jaeger_propagator::Propagator module
…lementation of TextMapPropagator::fields()
…ELOG.md's to reflect changes
…er-propagator/README.md
@cijothomas please let me know if this is what you had in mind for #995 (comment). I would especially be interested in getting feedback on the style/approach I've taken (ie: need more docs, additional unit tests are too granular). |
opentelemetry-jaeger/CHANGELOG.md
Outdated
## v0.21.0 | ||
|
||
### Changed | ||
- Move opentelemetry-jaeger::Propagator logic to its own crate (opentelemetry-jaeger-propagator) to prepare for opentelemetry-jaeger exporter deprecation [#1487](https://github.com/open-telemetry/opentelemetry-rust/pull/1487) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets be more descriptive here to smoothen migration.
This crate previously contained two functionalities - an exporter to Jaeger, and a Jaeger propagator. Going forward, Jaeger propagator is shipped as new crate "crate-name"/link. The JaegerExporter will be deprecated after the next release, and users should use OTLP exporter instead. See "linktoexample" showing OTLPExporter with Jaeger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JaegerExporter will be deprecated after the next release, and users should use OTLP exporter instead. See "linktoexample" showing OTLPExporter with Jaeger.
+1. Let's just call out this create will be deprecate with only exporter in it.
@@ -41,9 +41,10 @@ exporting telemetry: | |||
```rust | |||
use opentelemetry::global; | |||
use opentelemetry::trace::Tracer; | |||
use opentelemetry_jaeger_propagator; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this readme file needs to updated to reflect it no longer has propagator and warning about exporter being removed in the next release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the opentelemetry-jaeger
readme to provide a warning about the upcoming deprecation of the Jaeger exporter and migration of the Jaeger propagator to a new crate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/open-telemetry/opentelemetry-rust/pull/1487/files#diff-d153afbd7102b8218509b0ce0b654c51ba1b8fee4c558c097f01226743a89870R7 need a small fix to remove propagator wording
opentelemetry-jaeger/CHANGELOG.md
Outdated
## v0.21.0 | ||
|
||
### Changed | ||
- Move opentelemetry-jaeger::Propagator logic to its own crate (opentelemetry-jaeger-propagator) to prepare for opentelemetry-jaeger exporter deprecation [#1487](https://github.com/open-telemetry/opentelemetry-rust/pull/1487) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JaegerExporter will be deprecated after the next release, and users should use OTLP exporter instead. See "linktoexample" showing OTLPExporter with Jaeger.
+1. Let's just call out this create will be deprecate with only exporter in it.
…er-propgator as the propgator functionality is not on track for deprecation at the moment
…phasize the current change, upcoming deprecation of the Jaeger exporter, and provide additional references
… about its upcoming deprecation and the migration of the Jaeger propagator functionality to a standalone crate
…test feature for future use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
We may need some more cleanups to make sure no leftovers exist that can cause confusion.
Thanks @cijothomas for the review and approval. Do we want to wait for TommyCpp and/or others to give a final review + approval before merging or is your approval enough. |
For trivial changes, one approval is good. This needs one more, to catch things one person may have missed! Lets wait for @TommyCpp to review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for working on this
Description
Create
opentelemetry-jaeger-propagator
to prepare foropentelemetry-jaeger
exporter deprecation (https://opentelemetry.io/blog/2022/jaeger-native-otlp/).This is the first step taken from #995 (comment) towards resolving #995.
Changes
opentelemetry-jaeger-propagator
libraryopentelemetry-jaeger::Propagator
module toopentelemetry-jaeger-propagator
Merge requirement checklist
CHANGELOG.md
files updated for non-trivial, user-facing changes