There is a decision tree rule to define so called critical alert events; IsACriticalAlert. you can login as aesdeveloper to check the logic. Looks like several thresholds are hardcoded, you would need to customize the rule if needed.
The UrgentEvents (Health Indicator) Status getting changed from "Normal" to "Urgent" quite frequently in Production for our Customer application. Since we have a subscribed to the email alerts whenever the Health Status change, we are receiving emails (say 30 to 40 per day).
So, I'm in process of identifying the Thresholds on which this Indicator gets evaluated. Looks like if more than '0' CriticalEventsCount occurs, we get an email alert. Trying to understand if there is any possibility to Tune this CriticalEventsCount value & bump it up slightly. Say to 3/4 ?
Somone please confirm if this is the right Decision Table that AES evaluates to showup the AES Enterprise - Health Status for UrgentEvents Indicator? Is it possible to override/modify this Decision Table ?
Decision Table: criticalEventsNode PegaAES-Data-NodeHealth ID criticalEventsNode RS PegaAES:07-12-01
Fine Tune the Logic of which AES generates the Critical Events. As per the update from Kevin -- this is the decision tree rule to define so called critical alert events IsACriticalAlert . but Is it possible to override/modify this Decision Tree ?
Also, can someone provide the logic/Rule on what basis it evaluates the critical error/exception events. It will be good to know.