-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Exception when specifying QUARKUS_OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=grpc #36084
Comments
/cc @alesj (grpc), @brunobat (opentelemetry,tracing), @cescoffier (grpc), @radcortez (opentelemetry,tracing) |
cuichenli you mean: |
nope, the value i set is |
Previously to Quarkus 3.3, with the previous exporter, there was only one protocol available. Setting that property has no effect. |
Sorry I may miss something here, but I thought to backport a fix we just need to update
to
The original code basically means if the protocol is set to Feel free to correct me if I am wrong. |
ok, it's just about the message, got it. |
I would like to work on this simple issue :) |
@siewp go for it! |
fixed by #36166 |
Describe the bug
When using the environment variable
QUARKUS_OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=grpc
Quarkus will throw exceptionI think this issue has been resolved in #35156 for 3.3.0, but for the older version, this is still causing issues. Can we implement a fix for the older versions?
Looks like the logic at
quarkus/extensions/opentelemetry/runtime/src/main/java/io/quarkus/opentelemetry/runtime/exporter/otlp/OtlpRecorder.java
Line 109 in cca68dd
grpc
instead?Thanks! Please feel free to correct me if I am getting any thing wrong here.
Expected behavior
No exception should be thrown
Actual behavior
Exception thrown
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: