Update OTel collector to v0.57.2 #1757
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
mapno
force-pushed
the
update-otel-collector
branch
from
8d457b3
to
3718e5f
Compare
mapno
force-pushed
the
update-otel-collector
branch
from
9416307
to
a050023
Compare
mapno
commented
Sep 26, 2022
|
This PR breaks propagation of the OTel tracer as we drop the opentracing bridge fork. |
mapno
requested review from
joe-elliott,
annanay25,
mdisibio,
kvrhdn and
zalegrala
as code owners
joe-elliott
approved these changes
Sep 26, 2022
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.
What this PR does:
Updates the OTel collector to v0.57.2. That is the latest version that is backwards compatible with the OTel proto changes introduced in #1754.
In order to remove the use of our internal OTel collector fork, some parts of the obsmetrics pkg have been copied over.
Which issue(s) this PR fixes:
Fixes #1746
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]