Skip to content

Conversation

@cijothomas
Copy link
Member

Mostly for SDK, rearranged changelings, grouping relevant ones together.

@cijothomas cijothomas requested a review from a team as a code owner February 7, 2025 17:50
@codecov
Copy link

codecov bot commented Feb 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.1%. Comparing base (34742d0) to head (41ee0dc).
Report is 2 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #2632   +/-   ##
=====================================
  Coverage   79.1%   79.1%           
=====================================
  Files        119     119           
  Lines      22556   22556           
=====================================
  Hits       17857   17857           
  Misses      4699    4699           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

- `opentelemetry::global::shutdown_tracer_provider()` removed from the API, should now use `tracer_provider.shutdown()` see [#2369](https://github.com/open-telemetry/opentelemetry-rust/pull/2369) for a migration example. "Tracer provider" is cheaply clonable, so users are encouraged to set a clone of it as the global (ex: `global::set_tracer_provider(provider.clone()))`, so that instrumentations and other components can obtain tracers from `global::tracer()`. The tracer_provider must be kept around to call shutdown on it at the end of application (ex: `tracer_provider.shutdown()`)
Note: Due to the large amount of making changes, check [migration guide to
0.28](../docs/migration_0.28.md) for a summary that can help majority users to
quickly migrate. The changelog below is the full list of changes.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense to group these changes based on the signals, and exporters this time, would be easy to users to see the relevant part which affects them?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

most changes affect multiple signals... But still I can do another reordering to get signals specific one close to each other

@lalitb lalitb merged commit b6783a1 into open-telemetry:main Feb 7, 2025
21 checks passed
bantonsson pushed a commit to bantonsson/opentelemetry-rust that referenced this pull request Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants