SA-18366

Summary

In AES - on the Enterprise Health screen, some systems do not display the correct production level. Instead of the correct value, a zero is displayed.

Error Messages

Not Applicable

Steps to Reproduce

1. Log in to AES
2. Navigate to Enterprise Health

Root Cause

A defect in Pegasystems’ code or rules causes this issue. If a monitored node is unable to determine its connection URL during startup, the production level gets set to 0 initially in AES. The connection URL can be manually updated in AES, however, the logic to set the production level is not using this updated URL and so the production level remains at 0.

Resolution

1. Log in to the AES server developer portal. Navigate to the app explorer screen and change the root class to PegaAES-Data-Nodes. Right click on the root class (class listed next to the leaf), and navigate to view > Instances. The "System" values should correspond with the different clusters found in AES. Look at the entries and verify that the connection strings are correct. If they are not, open these instances and then change the "New Connection String" to be the correct URL and save it.

2. Apply HFix-25412 to the AES server and restart the AES server along with the monitored node.