Problem: No health messages sent to the AES server
When no health messages are being sent to the AES server, either one or both of the following conditions might be the cause of this problem:
Legacy PRPC 6.x information for sending health messages to the AES server in the prlogging.xml and prconfig.xml files causes inconsistency.
The PegaAESREMOTE agent is not running on the monitored node.
AES : PEGA 7.2 version.
***Edited by Moderator: Marissa to update SR details***
I hope you have updated the Predictive Diagnostic Landing Page with correct AES URL in Pega 7.2 monitored node and all the aesremote agents are up and running. As from Pega 7.1.7 , we just need to update the Predictive Diagnostic Landing page.
1) Check the monitored node to see if it is configured correctly
a- from prsysmgmt, navigate to administration / configuration management
look for any entries for "management" topic (residual from Pega 62).
check value for "pdcconfig/altsoapurl" - is that the correct URL of the AES server?
try to call the URL specified by pdcconfig/altsoapurl from a browser. It should return HTTP/1.1 405 Method Not Allowed
b- in designer studio, go to landing page System / Settings / Predictive Diagnostic Cloud. Verify the URL and try the Test Connectivity Button
c- enable verbose logging of communications. From system management application / Logging and Tracing / Logging Level Settings or designer studio / systems / operations / logs / logging level settings, enable DEBUG for classes httpclient.wire.content and httpclient.wire.header. Look for HLTH0001 messages coming out of monitored node - are they successfully sent? Disable DEBUG logging after 15 minutes. There should be 7 HLTH0001 messages during this interval
d- if messages are sent from monitored node, on AES servers, enable verbose debugging for ParseAlertLine and parseHLTH0001 activities. See if HLTH0001 messages are received and processed by server
e- on AES system, look for dynamic system setting AES/SECURITY/AGENTS/NODEID . Verify that all PegaAES agents are running on that specific node. The agents will not actually do work on other nodes.
Posted: 3 years ago
Updated: 3 years ago
Posted: 22 Jun 2017 14:22 EDT Updated: 22 Jun 2017 14:39 EDT
"pdcconfig/altsoapurl" correctly configured and it returns HTTP 405 Method Not Allowed message after launching the URL in the browser.
b) I couldnt find Test Connectivity Button in the landing page System / Settings / Predictive Diagnostic Cloud.Not even in the pega help.
c) Couldnt find HLTH0001 messages in the Pega Logs after enabling DEBUG for classes httpclient.wire.content and httpclient.wire.header.Please find below for the communication established between AES server and Monitored nodes.
Regarding the PR nodes health information appear as Unknown(1) on AES server, would you recommend changing the condition on the Decision Table 'ServerStatus' for value "Minutes since last create date time" to ten minutes from five minutes .