-
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
OpenTelemetry vertx exporter wrongly parses the endpoint #35501
Comments
/cc @brunobat (opentelemetry), @radcortez (opentelemetry) |
Did this work properly in Quarkus 3.2? |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Aug 23, 2023
#35503 should fix the issue |
Not sure. I was using otlp exporter before. Now switching to cdi |
geoand
added a commit
that referenced
this issue
Aug 23, 2023
Take OTel exporter endpoint path into account
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Aug 26, 2023
Fixes: quarkusio#35501 (cherry picked from commit 3511999)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Aug 26, 2023
Fixes: quarkusio#35501 (cherry picked from commit 3511999)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
404 error code occur while submitting the traces to open telemetry api.
The issue is originated from
io.quarkus.opentelemetry.runtime.exporter.otlp.VertxHttpExporter
. The implementation extracts the host from the base uri and ignores the paths.Below a screenshot from my configurations and how it ended up in the exporter.
Expected behavior
I expect the client to parse the endpoint properly without ignoring paths in the URL
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
Darwin Mazens-MacBook-Pro.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000 arm64
Output of
java -version
17.0.8
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.3.0
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: