liqingwang opened a new issue #7992:
URL: https://github.com/apache/dolphinscheduler/issues/7992


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   Hi, All.
   
   We want to add an alert plugin named `PagerDuty` for DolphinScheduler. And 
we would like to contribute to the community.
   
   There is one question that needs to be discussed.
   
   There is two alert strategies `success` & `fail` for process or task. One 
record will be inserted in t_ds_alert when triggered. And the record doesn't 
contain the alert strategy. Other alert plugins don't care about alert 
strategy, they all send the title and content to where they are configured.
   
   And there is a param named `severity` in PagerDuty API, which in the 
official documentation means :
   
   > The perceived severity of the status the event is describing with respect 
to the affected system. This can be `critical`, `error`, `warning` or `info`.
   
   We think that when somebody configured the alert strategy of process or task 
is `success`, it means when the process or task succeeded, they just want a 
massage, this situation should use `severity: info` calls the PagerDuty API. 
   
   When they configured the strategy as `fail`, calling the PagerDuty Api with 
`critical` or `error` is better.
   
   But if support this case, we need to change the code. Add a column in the 
t_ds_alert table and change the logic insert the strategy field in this table 
when the alert strategy is triggered.
   
   ### Use case
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to