Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 3.1
edited by eMagiz
on 2022/06/10 10:53
Change comment: There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2024/08/14 12:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,12 +1,7 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{container}}{{container layoutStyle="columns"}}(((In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
2 2  
3 -In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
4 -
5 5  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
7 -* Last update: August 25th, 2021
8 -* Required reading time: 2 minutes
9 -
10 10  == 1. Prerequisites ==
11 11  
12 12  * Novice knowledge of the eMagiz platform
... ... @@ -15,57 +15,48 @@
15 15  
16 16  This microlearning is about cleaning up the Alerting as configured in the Manage phase. Alerts can be set on various ways and levels * please inspect the related microlearnings around alerting to understand more about that. During the cleanup of various systems, flows and runtime, the Alerting needs to remain current with the integration model.
17 17  
18 -
19 -
20 20  == 3. Cleanup the Alerting in Manage ==
21 21  
22 22  === 3.1 Scenario's when to cleanup the Alerting phase ===
23 23  
24 -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
25 -2. A specific runtime is removed from the integration model that is referenced in the Alerting
26 -3. A flow or integration is removed from the integration model that is reference in the Alerting
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
19 +* A specific runtime is removed from the integration model that is referenced in the Alerting
20 +* A flow or integration is removed from the integration model that is reference in the Alerting
27 27  
28 28  === 3.1 Steps to clean ===
29 29  
30 -Navigate to the Triggers first.
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.
31 31  
32 -1. Locate Queue specific
33 - 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 +**Queue specific**
34 34  
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 +
35 35  * Standard – Queue consumers too high
36 36  * Standard – Queue consumers too low
37 37  
38 -2. Locate Runtime specific
39 - 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 +**Runtime specific**
40 40  
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 +
41 41  * Standard – Data measurements missing
42 42  * Standard – Log entries missing
43 43  * Standard – Error log entry
44 44  
45 -3. Once you have located the candidates, update and/or remove the triggers relevant for update
46 -4. Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
47 -5. Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.
41 +* Once you have located the candidates, update and/or remove the triggers relevant for update
42 +* Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
43 +* Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.
48 48  
45 +== 4. Key takeaways ==
49 49  
50 -
51 -== 4. Assignment ==
52 -
53 -Determine whether you can clean up parts of the Alerts from the project that you work on. If so, execute the cleanup.
54 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
55 -
56 -== 5. Key takeaways ==
57 -
58 58  * Cleaning up the Alert phase is important to ensure no false positive alerts are created/used
59 59  * Review the Alert setting at each release to production (post deployment step) to keep things manageable
60 60  
50 +== 5. Suggested Additional Readings ==
61 61  
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"]]
62 62  
63 -== 6. Suggested Additional Readings ==
64 64  
65 -None
66 -
67 -== 7. Silent demonstration video ==
68 -
69 -None
70 -
71 71  )))((({{toc/}}))){{/container}}{{/container}}