-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Otel logging does not respond to it's config property. #46351
Labels
Milestone
Comments
/cc @radcortez (config) |
I'm having a look and I agree there's something wrong. From what I can see, there's also something incorrect with the metrics one. |
I created #46354 which should address this issue and the Metrics one too. |
I manually checked that the issue is indeed fixed now.. |
🙏🏽 |
gsmet
added a commit
to gsmet/quarkus
that referenced
this issue
Feb 24, 2025
Fixes quarkusio#46351 (cherry picked from commit 19f2ec6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Related to #38239 and docs https://quarkus.io/version/main/guides/opentelemetry-logging
Testing with quarkus main snapshot
According to docs, collector endpoint should be configured by property
quarkus.otel.exporter.otlp.logs.endpoint
. But extension does not react to this property. Instead it actually is configured by "quarkus.otel.exporter.otlp.traces.endpoint".In my setup I changed the grafana-otel-lgtm service to use different port than default 4317. Even when I configure it to the
quarkus.otel.exporter.otlp.logs.endpoint=http://localhost:32791
no logs arrive to the backend and app complains about not being able to connect to the port 4317:Problems with both logs and traces export is fixed, when I configure quarkus.otel.exporter.otlp.traces.endpoint.
From my testing it seems like property
quarkus.otel.exporter.otlp.logs.endpoint
is ignored entirely. Even when I set it to complete bogus likequarkus.otel.exporter.otlp.logs.endpoint=http://wtfWhatisThis:456123748
it works, as long as traces property is set correctly.Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
999-SNAPSHOT
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: