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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -14,16 +14,15 @@
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.
18 - ** The user may still be referenced in the notification settings and should be removed
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
19 19  * A specific runtime is removed from the integration model that is referenced in the Alerting
20 20  * A flow or integration is removed from the integration model that is reference in the Alerting
21 21  
22 22  === 3.1 Steps to clean ===
23 23  
24 -Once you have opened your model you should navigate to the Manage environment. From here you should open the Alerting section under Manage and select Triggers. Here you can change the relevant triggers.
23 +Navigate to the Triggers first.
25 25  
26 -**Queue specific**
25 +**Locate Queue specific**
27 27  
28 28  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
29 29  
... ... @@ -30,7 +30,7 @@
30 30  * Standard – Queue consumers too high
31 31  * Standard – Queue consumers too low
32 32  
33 -**Runtime specific**
32 +**Locate Runtime specific**
34 34  
35 35  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
36 36  
... ... @@ -42,16 +42,22 @@
42 42  * Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
43 43  * Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.
44 44  
45 -== 4. Key takeaways ==
44 +== 4. Assignment ==
46 46  
46 +Determine whether you can clean up parts of the Alerts from the project that you work on. If so, execute the cleanup.
47 +This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
48 +
49 +== 5. Key takeaways ==
50 +
47 47  * Cleaning up the Alert phase is important to ensure no false positive alerts are created/used
48 48  * Review the Alert setting at each release to production (post deployment step) to keep things manageable
49 49  
50 -== 5. Suggested Additional Readings ==
54 +== 6. Suggested Additional Readings ==
51 51  
52 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
53 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
54 -*** [[Standard Alerting eMagiz (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]
56 +None
55 55  
58 +== 7. Silent demonstration video ==
56 56  
60 +None
61 +
57 57  )))((({{toc/}}))){{/container}}{{/container}}