Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 12.1
edited by Eva Torken
on 2023/08/23 16:19
Change comment: There is no comment for this version
To version 2.1
edited by Erik Bakker
on 2022/06/10 08:37
Change comment: Imported from XAR

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 - Cleanup Alerting in Manage
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.etorken
1 +XWiki.ebakker
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,7 +1,13 @@
1 -{{container}}{{container layoutStyle="columns"}}(((In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
1 +{{container}}{{container layoutStyle="columns"}}(((
2 += Cleanup Alerting in Manage =
2 2  
4 +In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
5 +
3 3  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
4 4  
8 +* Last update: August 25th, 2021
9 +* Required reading time: 2 minutes
10 +
5 5  == 1. Prerequisites ==
6 6  
7 7  * Novice knowledge of the eMagiz platform
... ... @@ -10,46 +10,57 @@
10 10  
11 11  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.
12 12  
19 +
20 +
13 13  == 3. Cleanup the Alerting in Manage ==
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
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
25 +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
26 +2. A specific runtime is removed from the integration model that is referenced in the Alerting
27 +3. 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.
31 +Navigate to the Triggers first.
25 25  
26 -**Queue specific**
33 +1. Locate Queue specific
34 + 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
27 27  
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 -
30 30  * Standard – Queue consumers too high
31 31  * Standard – Queue consumers too low
32 32  
33 -**Runtime specific**
39 +2. Locate Runtime specific
40 + 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
34 34  
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 -
37 37  * Standard – Data measurements missing
38 38  * Standard – Log entries missing
39 39  * Standard – Error log entry
40 40  
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.
46 +3. Once you have located the candidates, update and/or remove the triggers relevant for update
47 +4. Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
48 +5. 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 ==
46 46  
51 +
52 +== 4. Assignment ==
53 +
54 +Determine whether you can clean up parts of the Alerts from the project that you work on. If so, execute the cleanup.
55 +This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
56 +
57 +== 5. Key takeaways ==
58 +
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 ==
51 51  
63 +
64 +== 6. Suggested Additional Readings ==
65 +
52 52  None
53 53  
68 +== 7. Silent demonstration video ==
54 54  
70 +None
71 +
55 55  )))((({{toc/}}))){{/container}}{{/container}}