chore: bump otel to 128 #2059
Merged
mariomac merged 2 commits intorelease-2.2from Jun 18, 2025
Merged
Conversation
3668103 to
08a149c
Compare
This file contains hidden or 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
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.
As part of my attempts to upgrade otel to 128 in alloy, I've tried to compile alloy with a beyla from main branch and it turned to be not as trivial as just bumping beyla version(i did not spend much time trying, something was missing in opentelemetry-ebpf-instrumentation, probably the files that are expected to be generated).
This draft PR backports otel upgrade to the
release-2.2branch so that later in alloy I can upgrade otel without doing a big upgrade of beyla.https://raintank-corp.slack.com/archives/C066YDK2KLL/p1750068937303339