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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OTLP/HTTP+JSON Protocol exporter #810
Add OTLP/HTTP+JSON Protocol exporter #810
Changes from all commits
5e91f3e
ad3a6cf
dcc66c6
5e502df
2cdf438
d4d3459
eaca36e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why upgrade this to 1.33? I think 1.34 is used in our CI.
opentelemetry-cpp/ci/setup_grpc.sh
Line 16 in 0f6199f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 1.33 is the only version support both bazel 4+ and legacy gcc 4.8.
setup_grpc.sh
is only used when using cmake, not bazel.I found grpc 1.34 upgrade abseil-cpp to
2020923.2
and it uses something gcc 4.8 do not support.I submit another PR #666 and try to upgrade gRPC but failed on legacy toolchain. Maybe some one can help to switch the
grpc to old version or just disable OTLP Exporters when using bazel?I'm not familar with bazel.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume for Windows, while eventually getting to prebuilt DLL / SDK, we can most likely use whatever recent version of gRPC from vcpkg? Mine right now is 1.37.0
I hope that one works with Visual Studio 2015 Update 2 and above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested several toolchains with different versions of gRPC, and here is the result:
Right now, we have legacy gcc 4.8 in CI matrix, so I just update gRPC in bazel to 1.33 for compatiability. Maybe it can be upgraded to newer version in the future and in another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need that level of granularity, can one flag build both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is rare for one build to have both, so 2 flags make sense. Or we could introduce a third flag
WITH_OTLP
to include both but then it seems over complicated.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sometimes we want only either
WITH_OTLP_GRPC
orWITH_OTLP_HTTP
.Set
WITH_OTLP=ON
will try to turnWITH_OTLP_GRPC
on when grpc is found and turnWITH_OTLP_HTTP
on when both libcurl and nlohmann_json are found in this PR.The
WITH_OTLP
option is just for backward compatibility, and the actually options take effect isWITH_OTLP_GRPC
andWITH_OTLP_HTTP
now.