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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,7 +1,12 @@
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 2  
3 +In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
4 +
3 3  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
4 4  
7 +* Last update: August 25th, 2021
8 +* Required reading time: 2 minutes
9 +
5 5  == 1. Prerequisites ==
6 6  
7 7  * Novice knowledge of the eMagiz platform
... ... @@ -10,35 +10,39 @@
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  
18 +
19 +
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. 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
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
20 20  
21 21  === 3.1 Steps to clean ===
22 22  
23 23  Navigate to the Triggers first.
24 24  
25 -* Locate Queue specific
32 +1. Locate Queue specific
26 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
27 27  
28 - ** Standard – Queue consumers too high
29 - ** Standard – Queue consumers too low
35 +* Standard – Queue consumers too high
36 +* Standard – Queue consumers too low
30 30  
31 -* Locate Runtime specific
38 +2. Locate Runtime specific
32 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 - ** Standard – Data measurements missing
35 - ** Standard – Log entries missing
36 - ** Standard – Error log entry
41 +* Standard – Data measurements missing
42 +* Standard – Log entries missing
43 +* Standard – Error log entry
37 37  
38 -* Once you have located the candidates, update and/or remove the triggers relevant for update
39 -* Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
40 -* Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.
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 41  
49 +
50 +
42 42  == 4. Assignment ==
43 43  
44 44  Determine whether you can clean up parts of the Alerts from the project that you work on. If so, execute the cleanup.
... ... @@ -49,6 +49,8 @@
49 49  * Cleaning up the Alert phase is important to ensure no false positive alerts are created/used
50 50  * Review the Alert setting at each release to production (post deployment step) to keep things manageable
51 51  
61 +
62 +
52 52  == 6. Suggested Additional Readings ==
53 53  
54 54  None