-
Notifications
You must be signed in to change notification settings - Fork 472
feat: Tracehandle implementation for tracing in GCSFuse #4235
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: master
Are you sure you want to change the base?
Conversation
|
/gemini review |
|
/gemini summary |
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.
Code Review
This pull request introduces a TraceHandle interface to abstract tracing logic, providing both an OpenTelemetry-based implementation and a no-op implementation. This is a great improvement as it allows tracing to be disabled with minimal performance overhead. The new traceHandle is correctly plumbed through most of the application stack. The code is well-structured, and the use of constants for trace names and attributes is a good practice. I've identified a critical issue in the test setup that prevents tests from running, and a couple of other areas for improvement.
Summary of ChangesThis pull request significantly refactors the tracing mechanism within GCSFuse by introducing a flexible Highlights
Changelog
Activity
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4235 +/- ##
===========================================
+ Coverage 0 82.97% +82.97%
===========================================
Files 0 159 +159
Lines 0 19210 +19210
===========================================
+ Hits 0 15940 +15940
- Misses 0 2674 +2674
- Partials 0 596 +596
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Add traceHandle implementation support as custom no-op implementation for tracing in GCSFuse to reduce the impact w.r.t performance or time spent when tracing is disabled.
Link to the issue in case of a bug fix.
b/454481823
b/473717049
Testing details
Manually verified that the fs-ops traces are being exported to google cloud as usual and as expected.
Any backward incompatible change? If so, please explain.
NA