-
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
Can't use @SpanAttribute
annotation with Websockets.NEXT @OnTextMessage
#43412
Comments
@edeandrea OpenTelemetry is not fully supported yet. There's an open enhancement issue: #39143 |
|
Well, but it depens on how it's implemented. In WS Next the validation would most likely fail because it's an unsupported method parameter. I guess that normally it's "injected" by the interceptor, right? |
This comes from the OTel spec. The annotation is just used to extract, in the example above, the following key pair and place it in the attributes of the span: |
Wouldn't/shouldn't it just call |
I do understand that it's mandated by the spec. What I'm saying is that the validation of the WS next callback method will fail because it has some special requirements. I was asking about the implementation because a regular CDI interceptor would not work. |
Still on the backlog and no plans to develop it soon. |
Describe the bug
When combining WebSockets.NEXT & OpenTelemetry, I can't seem to be able to add an
@SpanAttribute
annotation to a method parameter of an@OnTextMessage
, like this:Expected behavior
No response
Actual behavior
I get this error when trying to run dev mode:
How to Reproduce?
Reproducer: parasol-insurance.zip
cd parasol-insurance
./mvnw clean quarkus:dev
Output of
uname -a
orver
Darwin edeandrea-m1pro 24.0.0 Darwin Kernel Version 24.0.0: Mon Aug 12 20:51:54 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6000 arm64
Output of
java -version
Quarkus version or git rev
3.14.4
Build tool (ie. output of
mvnw --version
orgradlew --version
)Additional information
No response
The text was updated successfully, but these errors were encountered: