| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
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. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.Context and Scope in 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 expected hello dependency 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: