Preserve Azure SDK tracing in OpenTelemetry 2.30 update - #4842
Conversation
|
Suraj Rajan (@skrcode) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
1 similar comment
|
Suraj Rajan (@skrcode) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
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.