[GitHub] [dolphinscheduler] lenboo edited a comment on issue #7992: [Feature][Alert] Support PagerDuty Plugin && Alert module judging strategy

[GitBox <gi...@apache.org>]

lenboo edited a comment on issue #7992:
URL: https://github.com/apache/dolphinscheduler/issues/7992#issuecomment-1014266303


   @liqingwang Good job!
   
   _Add alert_strategy in t_ds_alert table_
   
   According to my understanding, this field should be "process/task state"? 
   When process/task finish, alert can only be triggered once, and 't_ds_alert' will only have one data about this process/task.
   
   > 3. Change the code to bind the alert alarm instance strategy to process strategy
   > Bind alarm instance's strategy to t_ds_process_instance's warning_type and t_ds_schedules's > warning_type.
   
   > When a process with a configured notification strategy triggers an alert. A new record will insert > in t_ds_alert table saving the triggered strategy, whether the process is successful or failure. The > configured warning group will be triggered. The alarm instance will be triggered one by one.
   
   > And there is a new logic. Only process's strategy is matched alarm instance's strategy. The alert > will be sent, otherwise, the alert will be ignored._
   
   The alert instances can be sent according to state and strategy. 
   At the same time, we need to consider not only success and failure, but also others, such as pause and stop, and possible increase in the future
    
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org