-
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
[Extension Proposal] digma-quarkus-opentelemetry #29864
Comments
/cc @aloubyansky(extension-proposal), @brunobat(opentelemetry), @gastaldi(extension-proposal), @gsmet(extension-proposal), @maxandersen(extension-proposal), @radcortez(opentelemetry) |
interesting, but does this require a separate extension to add those items? /cc @brunobat On the repo then the recommended naming convention is |
It shouldn't require a separate extension. Our strategy with OTel is to put everything in one extension because it would be tricky for the user to know which extensions to add for OTel to work correctly. I would oppose it if this were a feature outside the OTel specification, but it is part of the OTel spec. I think we should be able to add the span attributes to some of the span instrumenters. Getting the executing method / classname for REST is possible. Not sure about other components. |
@radcortez , if that is the case I will create a Pull request on the main project on the original extension. ok? |
Sure, please go ahead. |
Thanks for clarifying this. Closing this issue now |
Description
digma.ai wants to extend the existing quarkus-opentelemetry ,
mainly by adding span attributes for the web controller - and its mapped method (and class).
see OTEL Semantic conventions for Source Code attributes
Interested in this extension, please +1 via the emoji/reaction feature of GitHub (top right).
Repository name
digma-quarkus-opentelemetry
Short description
add span attributes of code.function and code.namespace
Repository Homepage URL
https://quarkiverse.github.io/quarkiverse-docs/digma-quarkus-opentelemetry/dev/
Repository Topics
Team Members
GitHub Applications?
Additional context
No response
The text was updated successfully, but these errors were encountered: