Changes for page Dynamic Alerting
Last modified by Danniar Firdausy on 2024/11/19 11:08
From version 39.14
edited by Danniar Firdausy
on 2024/07/29 14:20
on 2024/07/29 14:20
Change comment:
There is no comment for this version
To version 39.7
edited by Danniar Firdausy
on 2024/07/29 14:03
on 2024/07/29 14:03
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -32,14 +32,15 @@ 32 32 33 33 == 3. Dynamic Alerting == 34 34 35 -To enhance the observability of your integration landscape while running in the current generation runtime architecture, we provide a functionality in the Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers in your environment. Fromthereon, you can navigateto the "Other"tab.35 +To enhance the observability of your integration landscape while running in the current generation runtime architecture, we provide a functionality in the Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers in your environment. On the top of the list, you will see all [["static" alerts>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] as defined by eMagiz below that you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete. 36 36 37 - Here,on the top ofthelist, you will see all [["static" alerts>>doc:Main.eMagizAcademy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]that are defined by eMagiz (alerts that are non-editable).And, below that (alertsthat areditable), you will see all "dynamic"alerts thatyou and your fellow team members(with sufficient rights) can view, edit and delete.37 +We offer alerting on seven types. 38 38 39 -In this page, we offer alerting on four types. 40 - 41 41 * Error message 42 42 * Log message 41 +* Queue consumers 42 +* Messages in queue 43 +* Queue throughput 43 43 * Messages added to topic 44 44 * Topic consumer messages behind 45 45 ... ... @@ -47,8 +47,6 @@ 47 47 48 48 First, we will discuss the configuration of each trigger type. Subsequently, we will discuss defining which recipients will be notified and how to alter the default congestion control settings (as this is the same for each trigger type). 49 49 50 -{{info}}As of the recent eMagiz release, we have moved the configurations for queue triggers (i.e., Queue consumers, Messages in queue, Queue throughput) to another page. Please refer to the [[Customize Queue alerting>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-customize-queue-alerting.WebHome||target="blank"]] page if you want to learn more on how to customize the triggers for these queues or the default values of these queue triggers.{{/info}} 51 - 52 52 === 3.1 Error message === 53 53 54 54 On top of the "static" alert that is autogenerated by eMagiz on Error messages, you can add additional "dynamic" alerts that only trigger when an error message is raised for which a specific header contains a particular value. This is most likely relevant when a specific error message with certain characteristics (i.e., a particular header value) needs to be sent to a different set of recipients.