Update the OpenTelemetry SDK version to 1.60.0#16407
Merged
Conversation
…g defaults The SDK 1.60.0 added a new default method isTraceIdRandom() to the TraceFlags interface. BridgedTraceFlags implements both the application and agent versions of TraceFlags, which causes a compilation error due to conflicting unrelated default methods. Adding an explicit override that delegates to the application's TraceFlags resolves the ambiguity.
…RecordBuilder150Incubator Add 'deprecation' to @SuppressWarnings on convertExtendedAttributes method to handle OtelDeprecatedApiUsage errors for deprecated ExtendedAttributes, ExtendedAttributesBuilder, and ExtendedAttributeKey usage. This is needed to support applications still using the EXTENDED_ATTRIBUTES feature.
SDK 1.60.0 sets the isTraceIdRandom bit in trace flags for randomly generated trace IDs, changing the value from 0x01 to 0x03. Update MDC tests to use span.getSpanContext().getTraceFlags().asHex() for expected values.
…new API method Compute the random trace ID flag from the byte value directly instead of delegating to the application's TraceFlags.isTraceIdRandom() which does not exist in API versions < 1.60. The previous implementation created a bytecode reference that muzzle detected as missing, causing all opentelemetry-api bridge instrumentation modules to be disabled.
…tomizer interface change DeclarativeConfigurationCustomizer is no longer a functional interface in SDK 1.60.0 (it now has addSpanExporterCustomizer, addMetricExporterCustomizer, and addLogRecordExporterCustomizer in addition to addModelCustomizer). Replace the lambda with an anonymous class implementation.
…terface change DeclarativeConfigurationCustomizer is no longer a functional interface in SDK 1.60.0. Replace lambdas with anonymous class implementations in SpanLoggingCustomizerProviderTest and ResourceCustomizerProviderTest.
Filter out otel.sdk.* metrics in metric assertions to avoid coupling tests to SDK internal self-diagnostics metrics which changed in 1.60.0.
The otel.experimental.config.file property is deprecated in SDK 1.60.0 and will be removed after 1.62.0. Rename all usages to otel.config.file. Also add the SDK deprecation warning to IGNORED_WARNINGS in the Spring smoke tests since the SDK may still emit it during initialization.
SDK 1.60.0 emits self-diagnostics metrics, so the exported metrics list contains more than just the test metric. Use anySatisfy instead of checking exact size to avoid coupling to SDK internal metrics.
36d48ff to
079f481
Compare
trask
approved these changes
Mar 7, 2026
laurit
approved these changes
Mar 9, 2026
xiang17
added a commit
to microsoft/ApplicationInsights-Java
that referenced
this pull request
Mar 11, 2026
xiang17
added a commit
to xiang17/ApplicationInsights-Java
that referenced
this pull request
Mar 11, 2026
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.
Update the OpenTelemetry SDK version to
1.60.0.