Add jaeger receiver #354
Closed
Add jaeger receiver #354
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
|
Hi @snikch , thanks for contributing the changes. AWS is also running the security review processes to add jaeger and zipkin receivers in AWS Distro of OTel collector. We'll merge this change once the review is complete. |
6 tasks
|
This is fixed in #423 and should go out in next release. |
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.
Description:
Adds the existing Jaeger receiver from the mainline otel collector.
Link to tracking Issue:
#292
This implements only the jaeger receiver.
Testing:
Ran locally and in ECS, confirmed traces are received and can be submitted to an otlp exporter.