PegaAESRemote agents @ monitored nodes and PegaAES agents @ AES are up and running.I could confirm that AES is receiving data from the reporting menu,recent snapshots in Enterprise Health and from reporting / custom reports.
The only difference between Compass_LT and other AES features working environments would be the additional PegaAESRemote agents enabled post PDC hotfixes installation @ Compass_LT. PFA for the screenshot.
PDC out of scope for now as we need to work upon masking our sensitive data in logs/application/database.
Posted: 2 years ago
Posted: 3 Jan 2019 21:59 EST
Andy Werden (WERDA)
Sr. Director, Product Management, Pega Application Management Suite
What sensitive data needs to be masked? The PegaRULES log does not get sent to PDC. The PARAM data in ALERT messages are whitelist filtered - any parameter not on the whitelist has value replaced by the literal [removed]. In general, that is sufficient to prevent PDC from getting sensitive data. Where do you see 'sensitive data' that needs to be scrubbed?
with regard to Compass_LT … if that is the only system not sending usage data to AES, back out the hotfix (delete the new rules / ruleset versions or update the PegaAESRemote access group to only use the old rules)
Posted: 2 years ago
Posted: 4 Jan 2019 14:46 EST
Pradeep Chowdary Pydi (PradeepPydi)
Senior PEGA DEVOPS and Cloud Administrator
I have tried rolling back the uncommitted PDC hotfixes via Hotfix Manager.Please provide detailed instructions regarding the following "delete the new rules / ruleset versions or update the PegaAESRemote access group to only use the old rules".
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.