Support Article

AES 7.2: Monitored nodes are not shown

SA-37819

Summary



Autonomic Event Services (AES)7.2 is used to monitor different Pega 7.2.2 systems.

Nodes belonging to a specific system are not visible in Enterprise Health and Quiesce pages included in the AES Manager Portal.

Alerts and Exceptions coming from these nodes are present in AES indicating a working communication from Monitored Nodes to AES.

The issue is not occurring with other monitored environments.


Error Messages



Not Applicable


Steps to Reproduce



Not Applicable


Root Cause



A defect or configuration issue in the operating environment.

AES Portal will show nodes in the Enterprise Health and Quiesce Landing Pages when nodes have corresponding PegaAES-Data-Indicator instances in the AES database.

PegaAES-Data-Indicator instances are created by the Monitor Health Status agent, running on AES, which in turn use PegaAES-Data-NodeHealth instances obtained from the HLTH0001 Health Messages sent by monitored nodes.

When HLTH0001 Messages from monitored nodes are not reaching AES, those nodes are not appearing in the AES Portal.

HLTH0001 Messages are produced by the management daemon running on the monitored node every two minutes and are sent to AES using a specific SOAP Appender.
In this specific case the issue has been caused by the usage of a non existing Soap Appender for health notifications.
This appender comes from a preexisting configuration and was still present in the prconfig.xml file, in entry:

<env name="management/notifications/appender" value="ALERT-AES-SOAP" />

Since Pega 7.1.7 onwards the recommended way to apply AES configuration in monitored nodes is to use the Predictive Diagnostic Cloud (PDC) landing page (Designer Studio > System > Settings > Predictive Diagnostic Cloud).

Changing the prlogging.xml and the prconfig.xml is not required and is not recommended.

Resolution



Perform the following local-change:
  1. Remove any pre-existing AES configuration from prlogging.xml and prconfig.xml.
  2. Configure the monitored node as described in the "Configuring the AES Nodes" chapter of the Autonomic Event Services (AES) Monitored Node Configuration Guide that applies to the AES version installed.


Published May 11, 2017 - Updated May 25, 2017

Have a question? Get answers now.

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