chore: update instrumentation list [automated]#16515
Conversation
otelbot-java-instrumentation
Bot
requested a review
from a team
as a code owner
| source_path: instrumentation/servlet/servlet-2.2 | ||
| scope: | ||
| name: io.opentelemetry.servlet-2.2 | ||
| schema_url: https://opentelemetry.io/schemas/1.37.0 |
There was a problem hiding this comment.
im not actually sure which PR caused this update
There was a problem hiding this comment.
Oh, interesting, from AI, but sounds legit:
The root cause was latent non-determinism from PR #15144 (Nov 2025) adding setSchemaUrl() only to the HTTP server instrumenter but not the response instrumenter, combined with findFirst() over a HashSet in the analysis code. Since EmittedScope.Scope.hashCode() includes schemaUrl and version, the version bump from 2.26.0-alpha-SNAPSHOT to 2.27.0-alpha-SNAPSHOT changed the hash codes of both scope entries, which altered HashSet iteration order and flipped which scope findFirst() returned.
There was a problem hiding this comment.
Fixed the determinism of the parsing here: #16546
Should we also add the schemaUrl to the response instrumenter?
There was a problem hiding this comment.
Should we also add the schemaUrl to the response instrumenter?
👍
otelbot-java-instrumentation
Bot
force-pushed
the
otelbot/metadata-update-main
branch
from
e92373d to
a561b26
Compare
2 participants
This PR was created automatically by the metadata update workflow.