We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using otel registry, OTEL_SERVICE_NAME should fall back to application name, if not provided in any other means.
If I don't specify OTEL_SERVICE_NAME I see this in NewRelic :
Instead I think this should behave like described in opentelemetry quarkus integration : https://quarkus.io/guides/opentelemetry
What do you think ?
The text was updated successfully, but these errors were encountered:
Here :
quarkus-micrometer-registry/micrometer-registry-otlp/runtime/src/main/java/io/quarkiverse/micrometer/registry/otlp/OtlpConfig.java
Line 73 in 53fa22d
But if OTEL_SERVICE_NAME is not set, it should fall back to ${quarkus.application.name}
Sorry, something went wrong.
@ebullient if you agree I can make a PR about this ...
Let me know Thank you
PRs are always welcome. ;)
No branches or pull requests
When using otel registry, OTEL_SERVICE_NAME should fall back to application name, if not provided in any other means.
If I don't specify OTEL_SERVICE_NAME I see this in NewRelic :
Instead I think this should behave like described in opentelemetry quarkus integration :
https://quarkus.io/guides/opentelemetry
What do you think ?
The text was updated successfully, but these errors were encountered: