-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
fix(events): Handle count_if(span.status) #96692
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
fix(events): Handle count_if(span.status) #96692
Conversation
wmak
commented
Jul 29, 2025
- I'm updating count_if to match discover's api in fix(events): Handle count_if(span.status) #96689, so for consistency adding the operator to all our existing -if combinator usage before deprecating it
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #96692 +/- ##
==========================================
+ Coverage 80.00% 80.70% +0.70%
==========================================
Files 8510 8498 -12
Lines 374625 373948 -677
Branches 24305 24266 -39
==========================================
+ Hits 299714 301805 +2091
+ Misses 74534 71766 -2768
Partials 377 377 |
static/app/views/insights/types.tsx
Outdated
@@ -498,7 +498,7 @@ type SpanResponseRaw = { | |||
} & { | |||
[Property in SpanNumberFields as `avg_compare(${Property},${string},${string},${string})`]: number; | |||
} & { | |||
[Property in SpanFields as `count_if(${Property},${string})`]: number; | |||
[Property in SpanFields as `count_if(${Property},equals,${string})`]: number; |
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 this should be
[Property in SpanFields as `count_if(${Property},equals,${string})`]: number; | |
[Property in SpanFields as `count_if(${Property},${'equals' | not_equals | etc.},${string})`]: number; |
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
- I'm updating count_if to match discover's api in #96689, so for consistency adding the operator to all our existing -if combinator usage before deprecating it
c6f3b8a
to
69fd725
Compare
Had to force push cause changing the base branch was leaving some hanging backend changes |
- I'm updating count_if to match discover's api in #96689, so for consistency adding the operator to all our existing -if combinator usage before deprecating it
- I'm updating count_if to match discover's api in #96689, so for consistency adding the operator to all our existing -if combinator usage before deprecating it