-
Notifications
You must be signed in to change notification settings - Fork 435
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
feat: clean up trace SDK APIs #1755
feat: clean up trace SDK APIs #1755
Conversation
2b94e6c
to
13bde88
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1755 +/- ##
=====================================
Coverage 74.4% 74.4%
=====================================
Files 122 122
Lines 19807 19800 -7
=====================================
Hits 14750 14750
+ Misses 5057 5050 -7 ☔ View full report in Codecov by Sentry. |
I think this update to opentelemetry-proto submodule is not intended, as we are already using the latest version :) |
2d64b24
to
683ec99
Compare
opentelemetry-sdk/CHANGELOG.md
Outdated
@@ -61,13 +65,7 @@ | |||
- After `shutdown`, `LogProcessor` will not process any new logs | |||
- Moving LogRecord implementation to the SDK. [1702](https://github.com/open-telemetry/opentelemetry-rust/pull/1702). | |||
- Relocated `LogRecord` struct to SDK, as an implementation for the trait in the API. | |||
- **Breaking** [#1729](https://github.com/open-telemetry/opentelemetry-rust/pull/1729) |
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.
we cannot remove this as it is already part of shipped code!
It seems unfortunate that this PR doesn't provide any kind of context or rationale in the description. This removes the See the code here: https://github.com/tokio-rs/tracing-opentelemetry/blob/v0.1.x/src/tracer.rs#L67. This ends up accessing |
Sorry for missing content in PR descriptions. As for way forward, we can either:
|
The rationale is mentioned in the changelog: https://github.com/open-telemetry/opentelemetry-rust/pull/1755/files#diff-14dfb7552119b2eca23adb12f587f7afba4f354c8dce5bcd2ae0e8a6a258e932R30-R31 It was unintentional to break @TommyCpp I am okay to revert the provider() part to prevent breaking The only way I see such issues from occurring again is by resolving #1571 |
By the way, It could be a good idea to doc comment the special accommodations for tokio tracing as mentioned in #1043, so that we will not unintentionally break them in the future. |
Alternatively if we want to provide the minimal capability via the Tracer API we could only export access to the id generator or even specifically new_trace_id() and new_span_id() methods. |
Submitted #1934. |
Close some API as they are not intended to expose to users. This helps us control the scope of GA release.
Changes
provider()
method as it's not suppose to expose to usersconfig()
method in favor ofDefault
implementationMerge requirement checklist
CHANGELOG.md
files updated for non-trivial, user-facing changes