Skip to content

feat(occurrences on eap): Implement tracing performance issues query#110722

Draft
shashjar wants to merge 1 commit intoshashjar/tracing-errors-query-double-read-occurrences-on-eapfrom
shashjar/tracing-performance-issues-query-double-read-occurrences-on-eap
Draft

feat(occurrences on eap): Implement tracing performance issues query#110722
shashjar wants to merge 1 commit intoshashjar/tracing-errors-query-double-read-occurrences-on-eapfrom
shashjar/tracing-performance-issues-query-double-read-occurrences-on-eap

Conversation

@shashjar
Copy link
Member

Implements double reads of occurrences from EAP for the performance issues query in src/sentry/snuba/trace.py.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Mar 16, 2026

# Group by (issue_occurrence_id, project_id) and collect group_ids,
# mirroring the legacy groupArray(group_id) aggregation
# TODO: is there a better way to do this?
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way to do this aggregation in the EAP query itself (might require array aggregate support)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant