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.
Problem Statement
The
is:escalatingissue 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:escalatingshould correlate with a recent increase in frequency or impact over an appropriate short-term window (e.g., minutes or hours), orIt 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.