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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor AttributesExtractor so that it extracts route from Context #5288
Refactor AttributesExtractor so that it extracts route from Context #5288
Changes from 1 commit
b83fc0b
6550e8e
930a296
7ac7d43
b2b40c6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about adding a
route(context, request, response)
to the getter interface (with a defaultHttpRouteHolder
implementation) but I decided against it:HttpRouteHolder
not only stores the route, but also renames the server span whenever the route is updated; if we were to allow somebody to implement aroute(context, request, response)
method that overrode the default implementation (and skipped theHttpRouteHolder
altogether), that instrumentation would not rename the server span after start -- and that would differ from how theHttpRouteHolder
handles things.In other words: using
route(request)
is fine, because theHttpSpanNameExtractor
handles that, but if you want to set the route during/at the end of the request you have to useHttpRouteHolder
.