Separate pekko route from http server instrumentation #15499
Merged
Conversation
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
trask
approved these changes
Dec 1, 2025
|
Thanks @laurit 👏 |
123liuziming
pushed a commit
to 123liuziming/opentelemetry-java-instrumentation
that referenced
this pull request
Dec 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Resolves #15457
In play applications
org.apache.pekko.http.scaladsl.server.PathMatchermight be missing which causes muzzle to fail for the server instrumentation. This PR moves the virtual field used by the route instrumentation out fromPekkoHttpServerSingletonsthat is used by the server instrumentation so that server instrumentation could work even when the classes for route instrumentation are missing. This is a regression from indy conversion.