Skip to content

fix(metric-issues): Show contributing issues for crash rate metric monitors#116703

Merged
malwilley merged 2 commits into
masterfrom
malwilley/crash-rate-detector-correlated-issues
Jun 5, 2026
Merged

fix(metric-issues): Show contributing issues for crash rate metric monitors#116703
malwilley merged 2 commits into
masterfrom
malwilley/crash-rate-detector-correlated-issues

Conversation

@malwilley

@malwilley malwilley commented Jun 2, 2026

Copy link
Copy Markdown
Member

Metric issues were only showing the "contributing issues" section for metric monitors targeting the errors dataset (like number of errors). It also makes sense to show this section for monitors targeting the sessions dataset, like "crash free user rate" since users will be looking for errors in the time range of the open period.

This matches the old alerts behavior, which also showed this section for crash free user/session rate alerts.

Show the contributing issues section for crash free rate (releases)
dataset detectors in addition to the errors dataset. This helps
users understand which issues are contributing to their crash rate.
@malwilley malwilley requested a review from a team as a code owner June 2, 2026 16:59
@malwilley malwilley changed the title feat(metric-issues): Show contributing issues for crash rate metric monitors fix(metric-issues): Show contributing issues for crash rate metric monitors Jun 2, 2026
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 2, 2026
@malwilley malwilley enabled auto-merge (squash) June 5, 2026 18:21
@malwilley malwilley merged commit e40ef04 into master Jun 5, 2026
70 checks passed
@malwilley malwilley deleted the malwilley/crash-rate-detector-correlated-issues branch June 5, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants