njnu-seafish opened a new issue, #18298: URL: https://github.com/apache/dolphinscheduler/issues/18298
### Search before asking - [x] I had searched in the [DSIP](https://github.com/apache/dolphinscheduler/issues/14102) and found no similar DSIP. ### Motivation When running manually or scheduling a run, you need to select an alert type first. If I configure alerts to be sent only on failure, do task timeouts or workflow timeouts count as cases where an alert should be sent? To avoid ambiguity, do we need to add a separate alert strategy for timeouts? Users can choose not to select any alert strategy, or select multiple ones. <img width="2436" height="1125" alt="Image" src="https://github.com/user-attachments/assets/7abcc221-e5e4-4459-a344-fc089fa46373"; /> ### Design Detail 1，WarningType includes the following types: SUCCESS(1), FAILURE(2),TIMEOUT(3) Additional types can be added in the future as needed. 2, Users can choose not to select any alert strategy, or select multiple ones. 3，The alert type is stored in the database as an array of selected values, for example, "1,3". 4，In scenarios like workflow success/failure, task timeout, or workflow timeout, the system evaluates the user's selected alert strategy to decide whether an alert should be triggered. ### Compatibility, Deprecation, and Migration Plan To maintain compatibility with the previous version's alert strategy, you can use the following migration strategy. Old version: NONE(0, "none") ---> New version: null Old version: SUCCESS(1, "success") ---> New version: SUCCESS(1, "success") Old version: FAILURE(2, "failure") ---> New version: FAILURE(2, "failure") Old version: ALL(3, "all") ---> New version: SUCCESS(1), FAILURE(2),TIMEOUT(3) ### Test Plan _No response_ ### 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]
