Use HTTP OTLP Exporter because it is architecture agnostic #185
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
NathanielRN
force-pushed
the
use-otlp-http-exporter
branch
8 times, most recently
from
1a51945 to
9a1d240
Compare
NathanielRN
force-pushed
the
use-otlp-http-exporter
branch
from
9a1d240 to
2cf1579
Compare
wangzlei
approved these changes
Nov 30, 2021
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
Follow up to #181 which does not download the
opentelmetry-exporter-otlp-grpcpackage because it downloaded C architecture specific code. We need to change the default exporter to be for HTTP as well. This is so we can distribute botharm64andamd64Lambda Layers without worrying about architecture specific code.