Issue with AES in version 7
SellPoint Browser Average Response and Weekly Performance Metrics is 0. This functionality needs to be reconfigured.
3 out of the Top 10 Performance Items are related to AES are AES issues:
- DB-135523 - Verify that the monitored nodes in this system are operating and reachable, so that this AES server can retrieve index information from them. Re... SQL:SELECT COUNT(DISTINCT "PC0".QUOTEKEY) AS...
- DB-135522 - Verify that the monitored nodes in this system are operating and reachable, so that this AES server can retrieve index information from them. Re... SQL:SELECT COUNT(DISTINCT "PC0".QUOTEKEY) AS...
- DB-135522 - Verify that the monitored nodes in this system are operating and reachable, so that this AES server can retrieve index information from them. Re... SQL:SELECT COUNT(DISTINCT "PC0".QUOTEKEY) AS...
Can AES team help with this?
<removed>
thanks
***Moderator Edit: Vidyaranjan | Removed PII***
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
Hi Frank,
We would recommend you create a support request on My Support Portal and get your AES alerts investigated further.
Thanks,
Harish
Pegasystems Inc.
IN
Hello!
Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Thank you,
Pegasystems Inc.
US
Are you using AES or PDC? If AES, which version?
What version of Pega Platform are you on?
Regarding missing interaction counts and average response times - Pega7 monitored nodes run AESRemote agents to push log-usage data to PDC/AES. Verify that the PegaAESRemote agents are running on all nodes.
If you are running Pega Platform 717+, check your prlogging.xml. If you customized it to integrate with AES/PDC, take the customization out - the dynamic appender in the core platform work ootb, are configured by a landing page, and changing the prlogging can break things
AES in turn uses agents to process data and update scorecard. Verify that AES agents are running on all nodes.
Re bad description/advice in DB* alerts.
1- If you ignore the bad description, the data in the alert is still relevant.
(a) how often the query is bad
(b) cost of the query being bad
(c) where the query comes from (rule). There are some bugs in AES/PDC SQL Parser that don't play well with Pega72+ on Postgres. They are on the list.
3- If platform is < 717, AES needs to SOAP-Back to platform to get information. From enterprise-management verify that the soap-back features (like agent list, requestor list, listener list) work for every node