-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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(performance): Adds trace_status_rate function to span metrics #70685
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #70685 +/- ##
==========================================
- Coverage 80.04% 80.03% -0.01%
==========================================
Files 6505 6505
Lines 290739 290742 +3
Branches 50102 50102
==========================================
Hits 232709 232709
- Misses 57593 57596 +3
Partials 437 437
|
"countIf", | ||
[ | ||
Column("value"), | ||
Function( | ||
"equals", | ||
[ | ||
Column("metric_id"), | ||
self.resolve_metric("span.self_time"), | ||
], | ||
), | ||
], | ||
), |
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.
To make this more robust, should we only count if there is a trace.status? Or can we just assume its always there?
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.
Hmm, good point. I thought about this for a bit and I think there might scenarios where we want to include spans that don't have a trace.status
. For cases where we only want to count spans that have a trace.status
, we should be able to just add something like has:trace.status
to the discover query to achieve that affect, so I think I'm going to leave this as is for the flexibility.
Adds trace_status_rate function to span metrics