getsentry / getsentry/sentry-java

Issue: is:escalating filter appears to misclassify issues during short-term spikes

未关闭
#5,355 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Android Feature Issues > Other
主要语言
Kotlin
星标
1.4k
派生
478
平均合并
2 天 23 小时
30 天内合并 PR
67

描述

### Problem Statement

The `is:escalating` issue filter does not appear to align with intuitive or expected behavior during short‑term error spikes. Issues returned by this filter are often not meaningfully “escalating,” even when there is a clear spike in errors over a shorter time window.

This makes it difficult to rely on the filter for operational triage during incidents

### Solution Brainstorm

One of the following would be expected:

- `is:escalating` should correlate with a recent increase in frequency or impact over an appropriate short-term window (e.g., minutes or hours), or
- The definition of “escalating” should be clarified if it is intentionally comparing broad timeframes (e.g., week-over-week).

It appears that escalation may be determined by comparing this week vs. last week, which may be too coarse for operational use during real-time incidents. e.g. an alert reviewing the last 15 mins showed a solid bump in count for issues, but none of the issues listed in the Alert showed as "escalating", even though one clearly has an increase in count.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。