Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 4.1
edited by Erik Bakker
on 2022/08/30 09:08
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
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,10 +1,7 @@
1 -In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
1 +{{container}}{{container layoutStyle="columns"}}(((In this microlearning, we'll take a look how to cleanup Alerting from an eMagiz project.
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
... ... @@ -17,30 +17,32 @@
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
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
23 23  
24 24  === 3.1 Steps to clean ===
25 25  
26 26  Navigate to the Triggers first.
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
25 +**Locate Queue specific**
30 30  
27 +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 +
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
32 +**Locate Runtime specific**
36 36  
34 +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 +
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.
40 +* Once you have located the candidates, update and/or remove the triggers relevant for update
41 +* Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
42 +* 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 45  == 4. Assignment ==
46 46  
... ... @@ -60,4 +60,4 @@
60 60  
61 61  None
62 62  
63 -)))((({{toc/}}))){{/container}}
62 +)))((({{toc/}}))){{/container}}{{/container}}