Skip to content

Bump OpenTelemetry SDK to 1.51.0, instrumentation to 2.17.0 and semconv to 1.34.0 #4532

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

Merged
merged 8 commits into from
Jul 7, 2025

Conversation

adinauer
Copy link
Member

@adinauer adinauer commented Jul 1, 2025

📜 Description

Bump:

  • opentelemetry-sdk to 1.51.0
  • opentelemetry-instrumentation to 2.17.0
  • opentelemetry-javaagent to 2.17.0
    -opentelemetry-semconv to 1.34.0

io.opentelemetry.semconv.SemanticAttributes has been removed in 1.30.0 so we can no longer use it to read the deprecated attributes. This however should be fine since we bumped the instrumentation dependencies as well

💡 Motivation and Context

Customers were reporting compile errors due to our outdated OTel version.

💚 How did you test it?

📝 Checklist

  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

@adinauer adinauer changed the title Bump OTel SDK to 1.51.0, instrumentation to 2.17.0 and semconv to 1.34.0 Bump OpenTelemetry SDK to 1.51.0, instrumentation to 2.17.0 and semconv to 1.34.0 Jul 1, 2025
Copy link
Contributor

github-actions bot commented Jul 1, 2025

Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against c3a761f

Copy link
Contributor

github-actions bot commented Jul 2, 2025

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 446.00 ms 483.40 ms 37.40 ms
Size 1.58 MiB 2.09 MiB 518.95 KiB

Previous results on branch: feat/bump-otel-1_51_0

Startup times

Revision Plain With Sentry Diff
ccbb30a 423.94 ms 464.22 ms 40.28 ms
228dd89 449.13 ms 465.16 ms 16.04 ms
f2bb552 412.40 ms 417.63 ms 5.23 ms
18428c8 452.84 ms 490.71 ms 37.88 ms

App size

Revision Plain With Sentry Diff
ccbb30a 1.58 MiB 2.09 MiB 518.94 KiB
228dd89 1.58 MiB 2.09 MiB 518.90 KiB
f2bb552 1.58 MiB 2.09 MiB 518.90 KiB
18428c8 1.58 MiB 2.09 MiB 518.93 KiB

adinauer and others added 2 commits July 3, 2025 11:23
…y changing OpenTelemetry defaults) (#4537)

* do not override span name if customized

* Format code

* log in case system property cannot be set

* merge

* changelog

---------

Co-authored-by: Sentry Github Bot <bot+github-bot@sentry.io>
# check https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/dependencyManagement/build.gradle.kts#L49 for release version above to find a compatible version
otelSemanticConventions = "1.28.0-alpha"
otelSemanticConventions = "1.34.0-alpha"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this have to be alpha or could we use a normal version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah good catch, I'll go through dependencies again to check which alpha versions have now been changed to non alpha.

Alpha used to mark the whole dependency as alpha. Previously there was no non alpha versions for some dependencies. This seems to have changed for at least semconv now: https://central.sonatype.com/artifact/io.opentelemetry.semconv/opentelemetry-semconv/versions

@adinauer adinauer merged commit 10ae067 into main Jul 7, 2025
34 checks passed
@adinauer adinauer deleted the feat/bump-otel-1_51_0 branch July 7, 2025 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants