Skip to content
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

Closed
mocenas opened this issue Feb 19, 2025 · 5 comments · Fixed by #46354
Closed

Otel logging does not respond to it's config property. #46351

mocenas opened this issue Feb 19, 2025 · 5 comments · Fixed by #46354
Labels
area/tracing kind/bug Something isn't working
Milestone

Comments

@mocenas
Copy link
Contributor

mocenas commented Feb 19, 2025

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:

Failed to export TraceRequestMarshalers. The request could not be executed. Full error message: Connection refused: localhost/127.0.0.1:4317
Failed to export LogsRequestMarshalers. The request could not be executed. Full error message: Connection refused: localhost/127.0.0.1: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 like quarkus.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 or ver

No response

Output of java -version

No response

Quarkus version or git rev

999-SNAPSHOT

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@mocenas mocenas added the kind/bug Something isn't working label Feb 19, 2025
Copy link

quarkus-bot bot commented Feb 19, 2025

/cc @radcortez (config)

@mocenas mocenas changed the title Otel logging does not respond to config property. Otel logging does not respond to it's config property. Feb 19, 2025
@gsmet
Copy link
Member

gsmet commented Feb 19, 2025

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.

@gsmet
Copy link
Member

gsmet commented Feb 19, 2025

I created #46354 which should address this issue and the Metrics one too.

@geoand geoand closed this as completed in 19f2ec6 Feb 19, 2025
@quarkus-bot quarkus-bot bot added this to the 3.21 - main milestone Feb 19, 2025
@mocenas
Copy link
Contributor Author

mocenas commented Feb 19, 2025

I manually checked that the issue is indeed fixed now..

@geoand
Copy link
Contributor

geoand commented Feb 19, 2025

🙏🏽

@gsmet gsmet modified the milestones: 3.21 - main, 3.19.1 Feb 24, 2025
gsmet added a commit to gsmet/quarkus that referenced this issue Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tracing kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants