Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 13.12
edited by Danniar Firdausy
on 2024/09/18 13:46
Change comment: There is no comment for this version
To version 13.13
edited by Danniar Firdausy
on 2024/09/18 13:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,7 @@
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 explore how to effectively clean up Alerting configurations within your eMagiz project. You will learn when and why to review and update your alerts to ensure they remain accurate and aligned with your integration model.
4 +
3 3  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
4 4  
5 5  == 1. Prerequisites ==
... ... @@ -46,8 +46,9 @@
46 46  
47 47  == 4. Key takeaways ==
48 48  
49 -* Cleaning up the Alert phase is important to ensure no false positive alerts are created/used
50 -* Review the Alert setting at each release to production (post deployment step) to keep things manageable
51 +* Regularly cleaning up the Alerting phase ensures the accuracy and relevance of alerts, preventing unnecessary or false positives.
52 +* Always review and adjust alert settings after model changes, such as the removal of users, runtimes, or flows, to maintain alignment with the integration model.
53 +* As part of your post-deployment routine, review your Alerting setting with each release to production to keep your model manageable and up to date.
51 51  
52 52  == 5. Suggested Additional Readings ==
53 53