Changes for page Topic Alerting
Last modified by Erik Bakker on 2025/11/19 20:30
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,11 +23,11 @@ 23 23 * Recipients are defined on the queue level. 24 24 25 25 == 3. Queue Alerting == 26 - Asdiscussedin theprevious[[microlearning>>doc:Main.eMagizAcademy.Microlearnings.CrashCourse.CrashCoursePlatform.crashcourse-platform-manage-alerting-gen3||target="blank"]],queue alerting refersto theconfiguration ofalerts thatworkby applyingauniformset of triggerstoallqueues inyourmodel.26 +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 within your model that are generated by eMagiz. Out-of-the-box, eMagiz provides the default values that are suitable for the topology of each of your model environments (Testing-Acceptance-Production). By topology here, we refer whether your environment is running on single-lane or double-lane setup. In the screenshot below, you can find the overview of your queue alerts by navigating to Manage -> Alerting -> Triggers. 27 27 28 28 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz-queue-alerts-overview.png]] 29 29 30 -Here, whenyounavigate to Manage->Alerting->Triggers, youwill find all the queues that are generated by eMagiz currently existing within your model, along with the trigger conditions and thresholds that are applied to each of these queues. In the following sections, we will discuss how you can tune these queue triggers to your needs.30 +Here, you will find all the queues that are generated by eMagiz currently existing within your model, along with the trigger conditions and thresholds that are applied to each of these queues. In the following sections, we will discuss how you can tune these queue triggers to your needs. 31 31 32 32 === 3.1 Customize Queue Alerting === 33 33