The first article is about alerts in a customer service application. I believe they have a different purpose. I am asking about actual alert log messages that tell you something about the performance and security. The second article explains the configuration of the prconfigxml-file. I do not see how the third article is related. Maybe i have not asked the right question? if elaboration is required, please let me know.
Posted: 4 years ago
Posted: 26 Mar 2018 11:32 EDT
Andy Werden (WERDA)
Senior Director, Product Management, Observability Services
NehaMittal - thank you for your suggestions but they do not pertain to Mohamed's questions.
Yes, you can create custom alerts that will be written to the PegaRulesALERT file and sent to PDC/AES.
Alerts may be generated using the alert method in the loghelper (oLog) java object. The method takes as input a delimited string that include the alert code, kpi threshold, kpi and alert message.
AES/PDC will store alerts regardless of whether AES/PDC have any logic to support a particular alert code. To support an alert there must be rules to parse and "correlate" each instance of an alert to determine the "unique essence" of each occurrence and create one action item for each unique issue. In the absence of parsing and correlation for a custom alert, AES/PDC will create a single action item case per system per alert code -- all instances of a custom alert in a given system will correlate to a single action item.
In AES, one can create custom rules to do parsing, correlation, advice, notifications, etc for a custom alert. In PDC, one does not have the ability to do custom rules, but the PDC team can add new capabilities if they will benefit multiple customers and improve the value of the service.