[Response Ops] Refactor alerting task runner - refactor determination of active/new/recovered alerts #131546
Labels
Feature:Alerting/RulesFramework
Issues related to the Alerting Rules Framework
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Meta issue: #124206
As a step towards refactoring the task runner, move the determination of new/active/recovered alerts to the
AlertFactory
. TheAlertFactory
contains all the information needed to make this determination. We should be able to add functions togetNewAlerts()
,getActiveAlerts()
andgetRecoveredAlerts()
and store it in the alert factory so even if they are called multiple times, the calculations are only done once. Keeping in mind that we should not be exposing these functions to the rule type executors (we want them only to usecreate()
anddone()
). We should also see if we can move the functionality intrackAlertDurations
into the alert factory sogetActiveAlerts()
returns alerts with updated duration andgetRecoveredAlerts()
returns alerts with updated duration and end time set.The text was updated successfully, but these errors were encountered: