Changes for page Dynamic Alerting

Summary

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

Details

Page properties

Content

...	...	@@ -25,7 +25,7 @@
25	25
26	26	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.
27	27
28		-We offer alerting on five types.
	28	+We offer alerting on seven types.
29	29
30	30	* Error message
31	31	* Log message
...	...	@@ -32,6 +32,8 @@
32	32	* Queue consumers
33	33	* Messages in queue
34	34	* Queue throughput
	35	+* Messages added to topic
	36	+* Topic consumer messages behind
35	35
36	36	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-trigger-options.png]]
37	37
...	...	@@ -97,7 +97,7 @@
97	97
98	98	=== 3.5 Queue througput ===
99	99
100		-On top of the "static" alert that is autogenerated by eMagiz on Error messages, you can add additional "dynamic" alerts that only trigger when the throughput on one or more queues is more or less than X messages per Y minutes. Subsequently, define whether on which queues (or all queues) you want eMagiz to check for this condition. No further action is needed if you want to check on all queues.
	102	+For this category you can add additional "dynamic" alerts that only trigger when the throughput on one or more queues is more or less than X messages per Y minutes. Subsequently, define whether on which queues (or all queues) you want eMagiz to check for this condition. No further action is needed if you want to check on all queues.
101	101
102	102	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-all-queues.png]]
103	103
...	...	@@ -119,8 +119,30 @@
119	119
120	120	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]]
121	121
122		-=== 3.6 Recipient(s) configuration ===
	124	+=== 3.6 Messages added to topic ===
123	123
	126	+For this category, you can add additional "dynamic" alerts. These alerts only trigger when the messages added to one or more topic is less than X messages per Y minutes. On top of the number of messages (X) and the timeframe (Y), you can define whether to validate this on a specific topic or all topics. Note that the default configuration is that the alert applies to all topics.
	127	+
	128	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-added-to-topic-all-topics.png]]
	129	+
	130	+You can uncheck the checkbox to check on a specific (set of) topic(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove topics to the trigger.
	131	+
	132	+{{info}}This process of adding and removing specific topics works identically, as explained in the previous section on "Queue throughput." {{/info}}
	133	+
	134	+For this trigger, additional criteria can be configured that allow you to define when eMagiz needs to validate this configuration (i.e., Occurence). With the help of this configuration option, you can specify when the trigger needs to be evaluated. An example could be only on Monday between 04:00 AM and 05:00 AM.
	135	+
	136	+=== 3.7 Topic consumer lag ===
	137	+
	138	+For this category, you can add additional "dynamic" alerts. These alerts only trigger when one (or more) consumer groups lag by X messages on one (or more) topic(s). Note that the default configuration is that you, as a user, need to specify for which topic(s) the alert applies, as consumers' behavior can vary widely.
	139	+
	140	+{{info}}This process of adding and removing specific topics works identically, as explained in the previous section on "Queue throughput." {{/info}}
	141	+
	142	+Once filled in, the solution should look similar as follows.
	143	+
	144	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-topic-consumer-lag-selected-topics.png]]
	145	+
	146	+=== 3.8 Recipient(s) configuration ===
	147	+
124	124	You can select your recipients when you switch from the "Trigger" to the "Output" tab. In this overview, you can choose both eMagiz users and external recipients.
125	125
126	126	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-recipient-config.png]]
...	...	@@ -127,7 +127,7 @@
127	127
128	128	{{info}}Note that when you define multiple external recipients, you need to separate each email address with a comma to make it work.{{/info}}
129	129
130		-=== 3.7 Congestion control configuration ===
	154	+=== 3.9 Congestion control configuration ===
131	131
132	132	In the same "Output" tab, you can also define the congestion control configuration. The default configuration is that congestion control will be activated once more than ten alerts are triggered in the last ten minutes. So should you want to reduce this number, you can do so here.
133	133
...	...	@@ -137,12 +137,14 @@
137	137
138	138	== 4. Key takeaways ==
139	139
140		-* There are five trigger options
	164	+* There are seven trigger options
141	141	** Error message
142	142	** Log message
143	143	** Queue consumers
144	144	** Messages in queue
145	145	** Queue throughput
	170	+** Messages added to topic
	171	+** Topic consumer messages behind
146	146	* On the trigger level, the recipients are defined
147	147	* On the trigger level, the congestion control is defined
148	148	* Default configuration of the congestion control is sufficient in most cases