Upgrade OTel to v0.91.0 #194
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
braydonk
requested review from
a team and
jefferbrecht
and removed request for
a team
jefferbrecht
approved these changes
Jan 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades OpenTelemetry Collector packages to v0.91.0. The only OTel API change we had to deal with is the change to
CollectorSettingsFactoriesfield, which now accepts a function that can return an error (essentially what ourcomponentsfunction already is).pdataandfeaturegatehave been released as v1.0.0, and no future collector packages will be released as release candidate thanks to the decision on open-telemetry/opentelemetry-collector#8063. This means I'm able to remove that restriction inupdate-components, and we can now use theupdate-otelmake target. I've adjusted the documentation to reflect this.