Changes for page Customize Queue 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 seven types.
	28	+We offer alerting on five types.
29	29
30	30	* Error message
31	31	* Log message
...	...	@@ -32,8 +32,6 @@
32	32	* Queue consumers
33	33	* Messages in queue
34	34	* Queue throughput
35		-* Messages added to topic
36		-* Topic consumer messages behind
37	37
38	38	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-trigger-options.png]]
39	39
...	...	@@ -99,7 +99,7 @@
99	99
100	100	=== 3.5 Queue througput ===
101	101
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.
	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.
103	103
104	104	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-all-queues.png]]
105	105
...	...	@@ -121,30 +121,8 @@
121	121
122	122	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]]
123	123
124		-=== 3.6 Messages added to topic ===
	122	+=== 3.6 Recipient(s) configuration ===
125	125
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		-
148	148	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.
149	149
150	150	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-recipient-config.png]]
...	...	@@ -151,7 +151,7 @@
151	151
152	152	{{info}}Note that when you define multiple external recipients, you need to separate each email address with a comma to make it work.{{/info}}
153	153
154		-=== 3.9 Congestion control configuration ===
	130	+=== 3.7 Congestion control configuration ===
155	155
156	156	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.
157	157
...	...	@@ -161,14 +161,12 @@
161	161
162	162	== 4. Key takeaways ==
163	163
164		-* There are seven trigger options
	140	+* There are five trigger options
165	165	** Error message
166	166	** Log message
167	167	** Queue consumers
168	168	** Messages in queue
169	169	** Queue throughput
170		-** Messages added to topic
171		-** Topic consumer messages behind
172	172	* On the trigger level, the recipients are defined
173	173	* On the trigger level, the congestion control is defined
174	174	* Default configuration of the congestion control is sufficient in most cases