Update OTEL Collector to v0.122.1 #4893
Merged
Conversation
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
joe-elliott
approved these changes
Mar 26, 2025
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
Breaking Changes
OpenTelemetry now enforces strict matching between receiver/exporter type and factory type. This is implemented here.
Receiver Name Changes
Receiver names are now more specific:
tempo/jaeger_receiverjaeger/jaeger_receiverImpact: This changes the
namedimension for the following metrics:tempo_receiver_accepted_spantempo_receiver_refused_spansOther Changes
Tempo Query
Internal reference updates:
"github.com/jaegertracing/jaeger/plugin/storage/grpc/shared""jaeger_spanstore "github.com/jaegertracing/jaeger/storage/spanstore"Translator/Jaeger
jaegerTrans.ThriftToTraces(batch)now accepts batches of type*jaeger.BatchJaeger proto and models
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]