-
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
Bump OpenTelemetry sdk to 1.42.1 #43752
Conversation
brunobat
commented
Oct 7, 2024
- Instrumentation to 2.8.0
- Semantic conventions to 1.27.0
- Point deprecated conventions to the new classes.
…nventions to 1.27.0
/cc @radcortez (opentelemetry) |
Do not merge for now, because of possible side effects on Microprofile Telemetry 2.0 certification. Set as draft. |
🎊 PR Preview 0545457 has been successfully built and deployed to https://quarkus-pr-main-43752-preview.surge.sh/version/main/guides/
|
Needed for #43678 |
Status for workflow
|
@brunobat after this change we see a See Karm/mandrel-integration-tests#266 (comment) Before:
After
Is this the expected behaviour? cc @Karm |
@zakkak that test seems to be the one related with sending real OTLP protocol data to the OpenTelemetry collector... You don't need to setup the collector, the test should do it out of the box with TestContainers and Docker, but for some reason, the sender request is not reaching the collector: |
That's intended AFAIK (@Karm please confirm). The question is, should the application report a SEVERE error in such cases? Till now it used to just print a WARNING. |
I'm afraid this comes from the upstream commit: open-telemetry/opentelemetry-java@1f6de35 |
## Description Bump quarkusVersion from 3.15.1 to 3.16.1 Quarkus 3.16 fixes the opentelemetry traces exporter issue: quarkusio/quarkus#43752