Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 9.1
edited by Erik Bakker
on 2022/08/30 09:49
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2022/08/30 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,32 +14,30 @@
14 14  
15 15  === 3.1 Scenario's when to cleanup the Alerting phase ===
16 16  
17 -* A user is no longer active on the integration model. The use may still be referenced in the notification settings and should be removed
18 -* A specific runtime is removed from the integration model that is referenced in the Alerting
19 -* A flow or integration is removed from the integration model that is reference in the Alerting
17 +1. A user is no longer active on the integration model. The use may still be referenced in the notification settings and should be removed
18 +2. A specific runtime is removed from the integration model that is referenced in the Alerting
19 +3. A flow or integration is removed from the integration model that is reference in the Alerting
20 20  
21 21  === 3.1 Steps to clean ===
22 22  
23 23  Navigate to the Triggers first.
24 24  
25 -**Locate Queue specific**
25 +1. Locate Queue specific
26 + If you have configured the alerting following the best practice outlined in the user guide for Alerting, the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
26 26  
27 -If you have configured the alerting following the best practice outlined in the user guide for Alerting, the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
28 -
29 29  * Standard – Queue consumers too high
30 30  * Standard – Queue consumers too low
31 31  
32 -**Locate Runtime specific**
31 +2. Locate Runtime specific
32 + If you are removing the last flow belonging to a system and you have followed the best practice outlined here the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
33 33  
34 -If you are removing the last flow belonging to a system and you have followed the best practice outlined here the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
35 -
36 36  * Standard – Data measurements missing
37 37  * Standard – Log entries missing
38 38  * Standard – Error log entry
39 39  
40 -* Once you have located the candidates, update and/or remove the triggers relevant for update
41 -* Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
42 -* Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.
38 +3. Once you have located the candidates, update and/or remove the triggers relevant for update
39 +4. Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
40 +5. Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.
43 43  
44 44  == 4. Assignment ==
45 45