Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Enterprise Health section does not show cluster and node details



Enterprise Health section under AESManager portal does not show cluster health information of PRPC nodes. And, AESDeveloper portal shows the instance of PegaAES-Data-Cluster class.


Error Messages


Steps to Reproduce

1. Update prlogging.xml of PRPC node to connect to AES Server.
2. Open AESDeveloper portal and check for instances of PegaAES-Data-Cluster. Confirm that cluster has been created.
3. Login to AESManager portal and open Enterprise Health section.

Root Cause

Monitor Health Status PegaAES agent was not running. No instances of PegaAES-Data-Indicator were found. 


Configure SMA to connect to AES node and navigate to Agent Management > Agents in SMA. Make sure all PegaAES agents are running specifically the Monitor Health Status PegaAES agent.


Published January 31, 2016 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us