Wiki source code of Customize Queue Alerting
Version 40.8 by Danniar Firdausy on 2024/07/18 14:46
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 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. | ||
| 3 | |||
| 4 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 5 | |||
| 6 | == 1. Prerequisites == | ||
| 7 | |||
| 8 | * Basic knowledge of the eMagiz platform | ||
| 9 | |||
| 10 | == 2. Key concepts == | ||
| 11 | |||
| 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. | ||
| 13 | |||
| 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. | ||
| 21 | |||
| 22 | == 3. Queue Alerting == | ||
| 23 | |||
| 24 | In principle, queue alerting refers to the configuration of alerts that work by applying a uniform set of triggers to all queues in your model. By queues here, we mean all queues that are generated by eMagiz and present in the Create phase of your model. This means that all of these queues by default have triggers configured for them. eMagiz | ||
| 25 | |||
| 26 | However, as a user, you can also further customize the trigger condition and thresholds for each of these queues. | ||
| 27 | |||
| 28 | == 3.1 Customize Queue Alerting == | ||
| 29 | |||
| 30 | |||
| 31 | |||
| 32 | == 4. Key takeaways == | ||
| 33 | |||
| 34 | * a | ||
| 35 | * b | ||
| 36 | * c | ||
| 37 | |||
| 38 | == 5. Suggested Additional Readings == | ||
| 39 | |||
| 40 | If you are interested in this topic and want more information, please read the help text provided by eMagiz. | ||
| 41 | |||
| 42 | )))((({{toc/}}))){{/container}}{{/container}} |