Wiki source code of Cleanup Alerting in Manage
Last modified by Danniar Firdausy on 2024/09/18 13:49
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 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 | |||
| 5 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 6 | |||
| 7 | == 1. Prerequisites == | ||
| 8 | |||
| 9 | * Novice knowledge of the eMagiz platform | ||
| 10 | |||
| 11 | == 2. Key concepts == | ||
| 12 | |||
| 13 | This microlearning is about cleaning up the Alerting as configured in the Manage phase. Alerts can be set on various ways and levels. During the cleanup of various systems, flows and runtime, the Alerting needs to remain current with the integration model. | ||
| 14 | |||
| 15 | {{info}}Please inspect the related microlearnings around [[alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] to understand more about that topic.{{/info}} | ||
| 16 | |||
| 17 | == 3. Cleanup the Alerting in Manage == | ||
| 18 | |||
| 19 | === 3.1 Scenarios when to cleanup the Alerting phase === | ||
| 20 | |||
| 21 | * A user is no longer active on the integration model. | ||
| 22 | ** The user may still be referenced in the notification settings and should be removed | ||
| 23 | * A specific runtime is removed from the integration model that is referenced in the Alerting | ||
| 24 | * A flow or integration is removed from the integration model that is reference in the Alerting | ||
| 25 | |||
| 26 | === 3.1 Steps to clean === | ||
| 27 | |||
| 28 | 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. | ||
| 29 | |||
| 30 | **Queue specific** | ||
| 31 | |||
| 32 | 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 | ||
| 33 | |||
| 34 | * Standard – Queue consumers too high | ||
| 35 | * Standard – Queue consumers too low | ||
| 36 | |||
| 37 | **Runtime specific** | ||
| 38 | |||
| 39 | 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 | ||
| 40 | |||
| 41 | * Standard – Data measurements missing | ||
| 42 | * Standard – Log entries missing | ||
| 43 | * Standard – Error log entry | ||
| 44 | |||
| 45 | Once you have located the candidates, update and/or remove the triggers relevant for update | ||
| 46 | * Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it. | ||
| 47 | * Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it. | ||
| 48 | |||
| 49 | == 4. Key takeaways == | ||
| 50 | |||
| 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. | ||
| 54 | |||
| 55 | == 5. Suggested Additional Readings == | ||
| 56 | |||
| 57 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links: | ||
| 58 | |||
| 59 | * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] | ||
| 60 | ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] | ||
| 61 | *** [[Standard Alerting eMagiz (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] | ||
| 62 | * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] | ||
| 63 | ** [[Alerting (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.WebHome||target="blank"]] | ||
| 64 | *** [[Dynamic Alerting (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]] | ||
| 65 | *** [[Customize Queue Alerting (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-customize-queue-alerting.WebHome||target="blank"]] | ||
| 66 | * [[Lifecycle Management (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22lifecycle+management%22||target="blank"]] | ||
| 67 | |||
| 68 | )))((({{toc/}}))){{/container}}{{/container}} |