Changes for page Cleanup Alerting in Manage
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 9.1
edited by Erik Bakker
on 2022/08/30 09:49
on 2022/08/30 09:49
Change comment:
There is no comment for this version
To version 12.1
edited by Eva Torken
on 2023/08/23 16:19
on 2023/08/23 16:19
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.etorken - Content
-
... ... @@ -14,15 +14,16 @@ 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 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 18 18 * A specific runtime is removed from the integration model that is referenced in the Alerting 19 19 * 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 - Navigate to the Triggersfirst.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. 24 24 25 -** LocateQueue specific**26 +**Queue specific** 26 26 27 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 28 ... ... @@ -29,7 +29,7 @@ 29 29 * Standard – Queue consumers too high 30 30 * Standard – Queue consumers too low 31 31 32 -** LocateRuntime specific**33 +**Runtime specific** 33 33 34 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 35 ... ... @@ -41,22 +41,14 @@ 41 41 * Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it. 42 42 * Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it. 43 43 44 -== 4. Assignment ==45 +== 4. Key takeaways == 45 45 46 -Determine whether you can clean up parts of the Alerts from the project that you work on. If so, execute the cleanup. 47 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment. 48 - 49 -== 5. Key takeaways == 50 - 51 51 * Cleaning up the Alert phase is important to ensure no false positive alerts are created/used 52 52 * Review the Alert setting at each release to production (post deployment step) to keep things manageable 53 53 54 -== 6. Suggested Additional Readings ==50 +== 5. Suggested Additional Readings == 55 55 56 56 None 57 57 58 -== 7. Silent demonstration video == 59 59 60 -None 61 - 62 62 )))((({{toc/}}))){{/container}}{{/container}}