-
Notifications
You must be signed in to change notification settings - Fork 423
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
Wrong build recipe generate a crash in OtlpHttpExporterFactory::Create #2458
Comments
Could you please provide the version of opentelemetry-cpp, the build system and |
Well, we are using the main - which is certainly not a good thing. Let me give the v1.13.0 a try. |
Yes, we use otel-cpp 1.11.0, gRPC v1.58.1, protobuf v24.2, curl 8.2.1 and openssl 3.1.2 with quic. We plan to upgrade all dependencies recently. |
Ok. The problem is fixed. Thanks for you help. I let you close this ticket. For the record, here is the recipe that works for me: ENV
CURL
OPENSSL
ABSEIL
PROTOBUF
gRPC
OPENTELEMETRY
|
Closing as can not reproduce. Thanks for the details. |
We have a c++ app offering the ability to choose between HTTP and gRPC to export its traces. It is consequently linked against
opentelemetry-cpp::trace
,opentelemetry-cpp::otlp_http_exporter
andopentelemetry-cpp::otlp_grpc_exporter
.We observe a crash in
opentelemetry::exporter::otlp::OtlpHttpExporterFactory::Create
when using a HTTP endpoint (see callstack below). There's no problem with a gRPC one.If we disable gPRC (at compile time) so that the application is no longer linked against
opentelemetry-cpp::otlp_grpc_exporter
, everything works fine and we can successfully instantiated our HTTP span exporter.So, it seems that the
opentelemetry-cpp::otlp_http_exporter
andopentelemetry-cpp::otlp_grpc_exporter
libraries don't coexist very well.Sorry if I missed a piece of documentation saying that what we try to achieve is not supported.
The text was updated successfully, but these errors were encountered: