-
Notifications
You must be signed in to change notification settings - Fork 2
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 disable is buggy #116
Labels
bug
Something isn't working
Comments
I will take a look. |
weird even from main if I do a checkout and then
cc @rmanibus |
@ggrebert i think i know its because GRPC itself its detecting it and initializing so you have to do.
I will update the docs |
melloware
added a commit
that referenced
this issue
Oct 23, 2024
melloware
added a commit
that referenced
this issue
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like the property
quarkus.temporal.telemetry.enabled=false
does not worksContext: #71
The devservice is working, but when the extension
quarkus-opentelemetry
is in the pom, there is some errors in the logs:When i try to disable the otel programaticaly or by properties, the result is the same.
But when the extension is not present, it works fine.
to reproduce the issue:
mvn -am -pl integration-tests/devservice quarkus:dev
The text was updated successfully, but these errors were encountered: