-
Notifications
You must be signed in to change notification settings - Fork 100
wip: capture spans for controllers automatically #282
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
base: main
Are you sure you want to change the base?
Conversation
a0dfbe3
to
8cd1747
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #282 +/- ##
============================================
- Coverage 80.83% 80.61% -0.22%
+ Complexity 1502 1457 -45
============================================
Files 128 123 -5
Lines 6183 5871 -312
============================================
- Hits 4998 4733 -265
+ Misses 1185 1138 -47 Flags with carried forward coverage won't be shown. Click here to find out more. see 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
if (\strpos($controllerName, '::') > 0) { | ||
list($class, $method) = \explode('::', $controllerName); | ||
if (isset($class, $method)) { | ||
hook( |
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 don't think this will work with modern runtimes, where one long-lived application might handle many requests.
Maybe it should just manually create and end span on Symfony events?
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 think I'd rather memoize the hooks already in place. - this hook in particular is for the controller callable
8cd1747
to
9f0c80f
Compare
No description provided.