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

Summary

Details

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