-
Notifications
You must be signed in to change notification settings - Fork 156
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
feat: name ActionPack spans with the HTTP method and route #123
Merged
arielvalentin
merged 6 commits into
open-telemetry:main
from
dmathieu:actionpack-span-naming-route
Oct 14, 2022
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
210ec56
feat: allow naming ActionPack spans with the HTTP method and route
dmathieu 09ddd37
feat: change default ActionPack span name to be METHOD ROUTE
dmathieu 5d1bfc1
fix: fix rails test with new span name
dmathieu 56ad898
only load the route if the span is recording
dmathieu 6862090
memoize the rails route to load only if necessary
dmathieu 068fa34
Merge branch 'main' into actionpack-span-naming-route
dmathieu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
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.
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.
For context I'm investigating a bug where I have evidence that this PR cause
request.script_name = "/"
, resulting in duplicate/
inrequest.url
e.g.request.url => "http://example.com//foo"
.I haven't fully pinpointed what is going on, but in the meantime this change seem very suspect.
If you
return
here then this memoization is never gonna work. So might be totally orthogonal, but this is very fishy.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.
So what is happening in our app is that we reach this line: https://github.com/rails/rails/blob/a51e9676e611f578bdfd10fcf6891d9e2d762a23/actionpack/lib/action_dispatch/journey/router.rb#L68
We end up matching a catch all engine (
#<ActionDispatch::Journey::Route:0x000000012f5ae0d0 @name="security_reports_engine" ...
) which isn't anchored, and cause this bug.Overall I don't think it's safe to call
recognize
where it's not expected.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.
@casperisfine do you have a suggestion for what this should do instead or is it unsafe to use recognize_route at all?
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'm not that familiar with the router, but yeah I'd suggest to wait for the router to be called by rails and grab the route there instead. (just a guess, might not be possible).
We just turned off that option.