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

AES Node shows offline



Monitored node shows up offline on Autonomic Event Services (AES) enterprise health console.

Error Messages

Not Applicable.

Steps to Reproduce

There is no specific use case to reproduce this issue.

Root Cause

The root cause of this problem is a defect in customer application code/rules. Monitored node does not have the required prconfig.xml or DSS values for it to be monitored by AES.


This issue is resolved through the following local-change: 

Add these entries in prconfig.xml:

       <env name="management/enabled" value="true" />
       <env name="management/interval" value="120" />
       <env name="management/notifications/appender" value="ALERT-AES-SOAP" />


Add DSS in Pega-Engine codeset:

key = "prconfig/management/enabled/default" value="true"
key = "prconfig/management/interval/default" value="120"
key = "prconfig/management/notifications/appender/default" value="ALERT-AES-SOAP"


Published August 13, 2015 - Updated October 8, 2020

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