Changes for page Dynamic Alerting

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -22,27 +22,24 @@
22	22	** Queue throughput
23	23	-->
24	24	{{/html}}
25		-* There are five trigger options
	25	+* There are four trigger options
26	26	** Error message
27	27	** Log message
28		-** Queue consumers
29		-** Messages in queue
30		-** Queue throughput
31		-
	28	+** Messages added to topic
	29	+** Topic consumer messages behind
32	32	* On the trigger level, the recipients are defined
33	33	* On the trigger level, the congestion control is defined
34	34
35	35	== 3. Dynamic Alerting ==
36	36
37		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our 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.
	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. From there on, you can navigate to the "Other" tab.
38	38
39		-We offer alerting on seven types.
	37	+Here, 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"]] that are defined by eMagiz (alerts that are non-editable). And, below that (alerts that are editable), you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete.
40	40
	39	+We offer alerting on four types.
	40	+
41	41	* Error message
42	42	* Log message
43		-* Queue consumers
44		-* Messages in queue
45		-* Queue throughput
46	46	* Messages added to topic
47	47	* Topic consumer messages behind
48	48
...	...	@@ -50,6 +50,8 @@
50	50
51	51	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).
52	52
	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	+
53	53	=== 3.1 Error message ===
54	54
55	55	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.