Wiki source code of Customize Queue Alerting

Version 40.7 by Danniar Firdausy on 2024/07/18 14:05

version	line-number	content
17.1	1	{{container}}{{container layoutStyle="columns"}}(((
40.7	2	In this microlearning, we will focus on how you can customize your queue alerts by configuring the trigger conditions and thresholds, which raise an alert and notify people when those points are passed. Should you want to learn more about the standard alerting that eMagiz offers, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3\|\|target="blank"]]. Note that the queue alerting explained in this page is only applicable for eMagiz models that are running the current generation runtime architecture.
1.1	3
17.1	4	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
1.1	5
	6	== 1. Prerequisites ==
	7
	8	* Basic knowledge of the eMagiz platform
	9
	10	== 2. Key concepts ==
	11
40.6	12	This microlearning focuses on customizing the queue alerts for each environment in your model. By customizing: we mean further configuring the trigger conditions and thresholds of your queues from the general default settings provided by eMagiz, so they better suit your needs and requirements.
1.1	13
40.7	14	* eMagiz applies the same set of triggers to all JMS queues
	15	* There are four queue trigger options that eMagiz currently provides:
	16	** Consumers check
	17	** Queue load check
	18	** Inactivity check
	19	** Periodic activity check
	20	* Recipients are defined on the queue level.
1.1	21
40.7	22	== 3. Queue Alerting ==
1.1	23
40.7	24	To enhance the observability of your integration landscape while running in the current 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.
1.1	25
35.1	26	We offer alerting on seven types.
1.1	27
30.1	28	* Error message
	29	* Log message
	30	* Queue consumers
	31	* Messages in queue
	32	* Queue throughput
35.1	33	* Messages added to topic
	34	* Topic consumer messages behind
1.1	35
30.1	36	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-trigger-options.png]]
1.1	37
32.1	38	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).
1.1	39
30.1	40	=== 3.1 Error message ===
1.1	41
32.1	42	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.
1.1	43
32.1	44	To define the trigger, fill in the header's name and the expected value. On top of that, you can fill in a description that will be added to the alert received via email. Once this is filled in, the configuration could look as follows.
1.1	45
30.1	46	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-error-message-configuration.png]]
1.1	47
30.1	48	=== 3.2 Log message ===
1.1	49
32.1	50	On top of the "static" alert that is autogenerated by eMagiz on Log messages, you can add additional "dynamic" alerts that only trigger when a log message contains a specific phrase. This is likely when you log something on which you want to alert when it happens.
1.1	51
32.1	52	To define the trigger, fill in the phrase you want to check. On top of that, you can fill in a description that will be added to the alert received via email. Once this is filled in, the configuration could look as follows.
1.1	53
30.1	54	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-log-message-configuration.png]]
1.1	55
30.1	56	=== 3.3 Queue consumers ===
1.1	57
32.1	58	On top of the "static" alert that is autogenerated by eMagiz on Queue consumers, you can add additional "dynamic" alerts that only trigger when the number of consumers on a (specific) set of queues is below a certain threshold.
1.1	59
32.1	60	To define the trigger, determine the threshold you want to check (i.e., 2). Subsequently, specify 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.
1.1	61
30.1	62	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-all-queues.png]]
1.1	63
32.1	64	You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger.
1.1	65
30.1	66	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-specific-queues.png]]
1.1	67
32.1	68	When you press the "Add" button, a new pop-up will appear through which you can select the queues for which you want the trigger to be activated. In this pop-up, you can choose one (or more) queues and press the "Select" button to add them to the trigger.
1.1	69
30.1	70	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection.png]]
	71
32.1	72	{{info}}Note that when you want to select multiple queues at once, you cannot press "Enter" to Save your selection. In this case, you need to press the "Select" button to save your choice.{{/info}}
30.1	73
32.1	74	Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
30.1	75
	76	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection-result.png]]
	77
	78	=== 3.4 Messages in queue ===
	79
32.1	80	On top of the "static" alert that is autogenerated by eMagiz on Messages in a queue, you can add additional "dynamic" alerts that only trigger when a queue holds more than X messages. Logically, the X can be determined by the user. 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.
30.1	81
	82	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-all-queues.png]]
	83
32.1	84	You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger.
30.1	85
38.1	86	{{info}}This process of adding and removing specific queues works identically, as explained in the section on Queue consumers.[[Queue consumers.>>\|\|anchor="H3.3Queueconsumers"]]{{/info}}
30.1	87
32.1	88	Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
30.1	89
	90	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-queue-selection-result.png]]
	91
	92	=== 3.5 Queue througput ===
	93
35.1	94	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.
30.1	95
	96	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-all-queues.png]]
	97
32.1	98	You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger.
30.1	99
38.1	100	{{info}}This process of adding and removing specific queues works identically, as explained in the section on Queue consumers.[[Queue consumers.>>\|\|anchor="H3.3Queueconsumers"]]{{/info}}
30.1	101
32.1	102	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.
30.1	103
	104	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]]
	105
35.1	106	=== 3.6 Messages added to topic ===
30.1	107
35.1	108	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.
	109
	110	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-added-to-topic-all-topics.png]]
	111
	112	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.
	113
38.1	114	{{info}}This process of adding and removing specific topics works identically, as explained in the section on Queue consumers.[[Queue consumers.>>\|\|anchor="H3.3Queueconsumers"]]{{/info}}
35.1	115
	116	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.
	117
	118	=== 3.7 Topic consumer lag ===
	119
	120	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.
	121
37.1	122	{{info}}This process of adding and removing specific topics works identically, as explained in the section on Queue consumers.[[Queue consumers.>>\|\|anchor="H3.3Queueconsumers"]]{{/info}}
35.1	123
	124	Once filled in, the solution should look similar as follows.
	125
	126	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-topic-consumer-lag-selected-topics.png]]
	127
	128	=== 3.8 Recipient(s) configuration ===
	129
32.1	130	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.
30.1	131
	132	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-recipient-config.png]]
	133
32.1	134	{{info}}Note that when you define multiple external recipients, you need to separate each email address with a comma to make it work.{{/info}}
30.1	135
35.1	136	=== 3.9 Congestion control configuration ===
30.1	137
32.1	138	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.
30.1	139
	140	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-congestion-control-config.png]]
	141
32.1	142	{{warning}}Note that we advise only reducing the number under the congestion control if the ten default is too high. We do not advise deactivating the congestion control as this can cause an explosion in the number of received notifications.{{/warning}}
30.1	143
	144	== 4. Key takeaways ==
	145
40.7	146	* a
	147	* b
	148	* c
30.1	149
	150	== 5. Suggested Additional Readings ==
	151
32.1	152	If you are interested in this topic and want more information, please read the help text provided by eMagiz.
30.1	153
17.1	154	)))((({{toc/}}))){{/container}}{{/container}}

Wiki source code of Customize Queue Alerting

Navigation