-
Notifications
You must be signed in to change notification settings - Fork 639
feat: Add snap_startTrace and snap_endTrace methods for performance tracing
#3519
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3519 +/- ##
=======================================
Coverage 98.24% 98.25%
=======================================
Files 408 410 +2
Lines 11537 11583 +46
Branches 1797 1801 +4
=======================================
+ Hits 11335 11381 +46
Misses 202 202 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
snap_startTrace and snap_endTrace methods for performance tracingsnap_startTrace and snap_endTrace methods for performance tracing
7b2785e to
81cf0b1
Compare
81cf0b1 to
4f95cb5
Compare
| }); | ||
| } | ||
|
|
||
| case 'startTrace': |
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.
Not for this PR, but we should add the metrics method to this Snap too so we can test it all
This adds two methods,
snap_startTraceandsnap_endTrace, intended to hook into the performance tracing functionality of Sentry. They are essentially wrappers of thetraceandendTracefunctions in the clients.