Question

AES: ParseAlertLine Failed to process alert.  Node check failed: Node ID:  Status: ** NodeNotFound

I'm getting 'ParseAlertLine Failed to process alert.  Node check failed: Node ID:  Status: ** NodeNotFound' error in the AES logs

What does it mean and what should be done to correct it?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
August 20, 2015 - 5:56am

It means that the Node ID in the alert being sent from the monitored node is not registered with AES.

  1. Please check to see that health messages are going to AES. In AES you can see instances of PegaAES-Data-NodeHealth
  2. Check your prlogging.xml file in the monitored node to see if its correctly configured to send health messages

Note: Node is registered with AES when PEGA0008 alert is sent or HLTH0001 health message is sent.

Comments

Keep up to date on this post and subscribe to comments

Pega
August 20, 2015 - 5:56am

It means that the Node ID in the alert being sent from the monitored node is not registered with AES.

  1. Please check to see that health messages are going to AES. In AES you can see instances of PegaAES-Data-NodeHealth
  2. Check your prlogging.xml file in the monitored node to see if its correctly configured to send health messages

Note: Node is registered with AES when PEGA0008 alert is sent or HLTH0001 health message is sent.

August 20, 2015 - 6:51am
Response to nistr

Are you using AES 3.4 or 3.5 to monitor Pega 7?