-
-
Couldn't load subscription status.
- Fork 4.5k
Description
Problem Statement
It's possible that somebody archives an issue incorrectly -- maybe for the wrong threshold, or for the wrong reason. We'd like to be able to detect when we have high-volume but archived issues so that we can address them. Without the ability to write an alert this seems impossible and depends on manually searching issues periodically.
In #80076 the fact that this could be done in Discover but not a Metric alert was (accidentally) fixed, which was the main blocker. However, with such a metric alert then the playbook needs to be to go and run some other query to get the actual issue. This also means that the alert must be routed to a central oncall, instead of the owning team for the archived issue.
Solution Brainstorm
- I can create an issue alert for incoming events inside an archived issue (with volume >x in past y timeframe) / I can set an issue alert to include archived issues
- this would likely involve more work than metric alerts as the filtering mechanism is different
- this enables a workflow where an alert can directly tell the triaging individual that a certain archived issue is too high volume
Product Area
Alerts
Metadata
Metadata
Assignees
Projects
Status