Support Article
AES Weekly Scorecard is incomplete for some production clusters
SA-58819
Summary
Autonomic Event Services (AES) is upgraded to AES 7.3, Pega 7.3.1, and WebLogic 12.1.3.
The Weekly Scorecard is incomplete for three of the four production clusters (that is, etopprod, dopegaprd, and BPA_PROD) monitored by AES. The scorecard is complete only for the pegappaes cluster (AES itself).
Error Messages
Not Enough Data
Steps to Reproduce
Not applicable
Root Cause
The AES system was monitoring a number of Production and UAT nodes. Some of these nodes displayed information in the Scorecard headers, while the others displayed 'Not enough data' for all the three categories.
The nodes that had problems were working earlier. These nodes were configured to communicate with the AES using the older prlogging.xml configuration type. This was configured with the ALERT-AES-SOAP and EXCEPTION-AES-SOAP appended.
Additionally, from the AES server perspective, the nodes did not have the necessary rows in pegaam_perf_stats to display any information. On the client side, the PushLogUsageData agent was running on all the four production nodes.
Resolution
Perform the following local-change:
- Use the Predictive Diagnostic Cloud landing page to configure the AES monitored nodes for later Pega 7 releases.
- Add the appenders for ALERT-AES-SOAP and EXCEPTION-AES-SOAP. This also creates an appender for AES-HEALTH-MSG.
Additionally, an enhancement request, FDBK-26656 is created for consideration by Pega Product Management.
Published December 29, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.