feat(otel): Add OpenTelemetry compatibility BOM#5629
Draft
adinauer wants to merge 2 commits into
Draft
Conversation
Add an opt-in Sentry OpenTelemetry BOM that imports the tested OpenTelemetry stable and alpha BOMs and constrains Sentry OpenTelemetry modules to the SDK version. Keep the main Sentry BOM from managing the dedicated OpenTelemetry BOM so regular Sentry consumers are unaffected.
Contributor
|
📲 Install BuildsAndroid
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📜 Description
Adds a dedicated
io.sentry:sentry-opentelemetry-bommodule. The new BOM imports Sentry's tested OpenTelemetry stable and alpha BOMs and constrains the published Sentry OpenTelemetry artifacts to the SDK version.The general
io.sentry:sentry-bomnow excludes*-bommodules so regular Sentry consumers do not implicitly opt in to OpenTelemetry version management.💡 Motivation and Context
Spring Boot and OpenTelemetry can manage different OpenTelemetry versions, which can cause runtime classpath mismatches for Sentry OpenTelemetry integrations. This provides an explicit opt-in BOM for customers who want Sentry's tested OpenTelemetry dependency set to win without changing dependency management for regular Sentry SDK users.
💚 How did you test it?
./gradlew spotlessApply apiDump./gradlew :sentry-opentelemetry:sentry-opentelemetry-bom:publishToMavenLocal :sentry-opentelemetry:sentry-opentelemetry-bom:spotlessCheck :sentry-bom:generatePomFileForMavenPublicationsentry-opentelemetry-bomPOM imports the OpenTelemetry stable, alpha, instrumentation, and instrumentation-alpha BOMssentry-bomPOM does not includesentry-opentelemetry-bom📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Add docs.sentry.io guidance for when to import
sentry-opentelemetry-bomand how to order it with Spring Boot dependency management.