Fix opentelemetry otlp integration #85
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
Add a configuration for the otel-collector that: * Receive incoming traces via grpc * Forward trace events to a jaeger collector, via grpc
* Ensure the name of the service originating the tracing events is properly propagated through by the otlp collector * Use the batch exported, the simple one has poor performance and is not recommended for production usage
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 fixes the integration with opentelemetry otlp collector. When we updated the project dependencies we introduced 2 regressions:
Finally, the PR adds a sample configuration file of otlp collector receiving events from policy-server and then sending them to a jaeger endpoint