Preserve Azure SDK tracing in OpenTelemetry 2.30 update - #4842
Closed
Suraj Rajan (skrcode) wants to merge 1 commit into
Conversation
Author
|
Closing in favor of the maintainer plan on #4821 to wait for aligned OpenTelemetry SDK, instrumentation, and contrib releases rather than retain a selective compatibility rollback. |
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.
Fixes the Azure SDK smoke-test regressions in #4821 without rolling back the OpenTelemetry SDK or the rest of the 2.30 instrumentation update.
OpenTelemetry Java instrumentation 2.30 added an Azure Core bridge whose muzzle references require
io.opentelemetry.context.ContextandScopein the application classloader. The Azure SDK smoke app intentionally has no direct OpenTelemetry API dependency, so the agent rejects the entire Azure Core instrumentation module as mismatched and the expectedhellodependency telemetry disappears.This keeps the upgraded 2.30 agent and replaces only its Azure Core 1.36 and 1.53 instrumentation slices with their 2.28.1 versions, which support Azure applications without an explicit OpenTelemetry API dependency. The dependency is strict so the 2.30 BOM cannot silently realign the compatibility artifact. This is scoped to the two modules changed by the upstream Azure context bridge (open-telemetry/opentelemetry-java-instrumentation#18886).
Verification:
1871dc7ebbe15dca7c42e587870b8b0153cb7e7e),AzureSdkTest$Tomcat8Java8Testtimes out because thehellodependency is absent; the same test passes with this commit.AzureSdkTestcontainer/JVM variants plusAzureSdkControllerSpansEnabledTest(9/9).methods,azure-functions, andapplicationinsights-web-2.3instrumentation test suites pass against the retained 2.30 agent../gradlew assemble spotlessCheckpasses (995 tasks)../gradlew test -x :agent:agent-tooling:testpasses. The full test command reaches 313 agent-tooling tests with only the pre-existing macOS-onlySystemInformationTest.testOsassertion failing; the same focused test fails on a clean checkout of the exact Bump the opentelemetry group across 1 directory with 11 updates #4821 head../gradlew resolveAndLockAll --write-locksand./gradlew generateLicenseReport --no-build-cachepass and produce no dependency-lock or license-content diff.