AES node is not monitoring exceptions in Pega 7.1.6 env
I have an AES 7.1.6 system which is monitored by AES Node ( Pega 7.2.2). I see that alerts and guardrail report data is monitored but the exceptions are not monitored by AES node. I added the exception appenders to prlogging.xml file as mentioned in AES_Node_Configuration_Guide_72-rev guide , all the agents in monitored and AES nodes are up and running.
I also see that DB indexes information is not available in the Alerts cases created by AES node.
Any help is appreciated.
***Updated by moderator: Lochan to update Categories; tag SR to post***
***Edited by Moderator Marissa to update platform capability tags****
Did the updated prlogging.xml solve issues with exceptions? I believe Pega 716 is the last version of Pega platform that sends exceptions to AES via the exception appender; exceptions are now handled as a form of alert (the EXCP0001 alert).
Regarding the missing index data - if the pushDBIndex agent is properly running on monitored nodes, it is possible that data is in AES but slightly corrupted. Query table pegaam_index. In the PDC service (which shares most rules with AES) we observed that a new parse-xml rule used in processing index information causes Pega to save the records to the table with a blank pxobjclass property - which makes the records invisible to any obj- operation or report looking for PegaAES-Data-Index records. Please confirm or deny that you have that possible bug and open an SR with notes if it is indeed happening
Please share your SR. Platform 716 has "dynamic appenders" built in but buggy. Platform 716 is the last version of Pega Platform where AES integration should be implemented through modification of prlogging.xml. Dynamic appenders and integration in prlogging can not be both enabled at same time.
Platform 716 may also be the last version of Pega platform with separate integration and processing of alerts and exceptions. Current platforms process exceptions through the EXCP0001 alert. In older platform versions, AES picked up exceptions through catching exceptions as they are being written to the PegaRules log file.