-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Crashtracker] Track active spans and traces #536
Conversation
BenchmarksThis comment was omitted because it was over 65536 characters.Please check the Gitlab Job logs to see its output. |
Library Vulnerabilities✅ No library vulnerabilities found (scanned 519f61c). |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #536 +/- ##
==========================================
- Coverage 70.63% 70.50% -0.14%
==========================================
Files 206 208 +2
Lines 28112 28397 +285
==========================================
+ Hits 19856 20020 +164
- Misses 8256 8377 +121
|
static ACTIVE_SPANS: AtomicU128Set<2048> = AtomicU128Set::new(); | ||
static ACTIVE_TRACES: AtomicU128Set<2048> = AtomicU128Set::new(); |
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.
Where did 2048 come from?
What does this PR do?
Provides a mechanism for clients to record active spans/traces, and reports them in the crashreport.
Motivation
Error-tracking said this would be useful to help corrlate crashes with the traces they affected.
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.