Be aware that there are issues deploying AES 73 on PRPC 731
PegaAES 73 can monitor Pega platform 55, 61, 62, 63, 71, 72, 73 and 731.
PegaAES 73 was developed and tested running on platform 73.
There appears to be a problem deploying Pega73 on platform 731 - the distribution media for AES 73 includes custom jar libraries in the root directory of the rulesets, while the platform is expecting that libraries will be in a /LIB sub-directory.
To install AES 73, one must use platform 73, or repackage the files to load on 731. The repackaging instructions will be posted to PDN shortly.
***Updated by moderator: Lochan to add Group Tags; mark as discussion***
Since i find this as the latest thread of AES/PDC, I would like to post a question here.
In our application we do use the ELK stack as well to monitor the logs. We are got a PDC account and configured lower environments to push data to PDC.
I am in the process of checking the sensitive data. What I found is Some of the ERROR logs which I see in Kibana is missing in PDC.
For eg: If there is a SOAP service, fail we have a custom logger in our connector activity, which logs the entire request along with the error message. I can see it in PegaRULES.log and the same line in Kibana.
But I dont find the line in PDC?! - Looks strange to me. As per the documentation all log levels >= ERROR should be there in PDC right? am I missing something here.