Question
ING Belgium SA NV
BE
Last activity: 12 Oct 2018 14:49 EDT
Enterprise health is not displayed for all the monitoring nodes
We had installed AES 7.3 recently in Pega 7.3.0 and observed that enterprise monitor doesn't show the health for all the nodes.
Enterprise Tab of AES manager portal -> not showing data for the monitoring nodes.
Followed Node configuration guide and did all the configurations(DASS, AES appenders in prlogging, AES agents and new connection string in node instances).
Kindly advice if i am missing something
***Edited by Moderator Marissa to update platform capability tags****
EPAM Systems, Inc.
ES
Hi Nagaraj,
Thanks for posting on PSC.
Just for initial stage investigation,
1. Navigate to "System Connectivity" landing page in Pega AES dashboard menu. Is log usage data is received?
2. In logs, are you able to see the data of nodes which aren't appearing on the dashboard?
Make sure all associated agent is up and running on monitored nodes, otherwise they won't send data to monitoring node.
Refer this video to isolate the probable root cause:- https://community.pega.com/video-library/support-guide-how-troubleshoot-commonly-faced-aes-monitoring-issues
Hope it helps you in troubleshooting issue faced at your end. Kindly notify if it does.
Regards,
Hi Nagaraj,
Thanks for posting on PSC.
Just for initial stage investigation,
1. Navigate to "System Connectivity" landing page in Pega AES dashboard menu. Is log usage data is received?
2. In logs, are you able to see the data of nodes which aren't appearing on the dashboard?
Make sure all associated agent is up and running on monitored nodes, otherwise they won't send data to monitoring node.
Refer this video to isolate the probable root cause:- https://community.pega.com/video-library/support-guide-how-troubleshoot-commonly-faced-aes-monitoring-issues
Hope it helps you in troubleshooting issue faced at your end. Kindly notify if it does.
Regards,
Asif
ING Belgium SA NV
BE
Hi Asif,
1.I can see log usage data in 'System Connectivity'
2.I could see all the node's data in log file.
3.Agents(PegaAES & RemoteAES) are up and running.
4.find all the configurations are good as per video . but one question
'New connection string' for PegaAES-Data-Node instances should be URL of each monitoring node or all should point to same AES server URL?
Pegasystems Inc.
IN
In PegaAES-Data-Node instances your Original Connection String should point to monitored node soap url’s .
If it’s not pointing to right url then modify it in New Connection String .
Also check the connectionstring column in pegaam_cluster_data table if all the monitored node url’s present .
Thanks,
Arun
Updated: 4 Jan 2018 14:38 EST
ING Belgium SA NV
BE
Its pointing to the right URL and the column 'connectionstring " is having monitored URL'S.
observed below error in log,
AES:07.30] ( internal.mgmt.Executable) ERROR sbelt10465.devbe.development|XX.XX.XX.XX |SOAP|PegaAES|Events|logAlert|A2D7F4D56BBE951DA56E6391C581EEB3E|Rule-Connect-SOAP.PegaAES-Data-Nodes.ExecuteMBeanOperation - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_719d12eef417d31fbbe542f1183a1237.step15_circum0
Please advice if i miss anything?
Pegasystems Inc.
IN
Hello Nagaraj,
In addition to what my colleague suggested, check if few or all the users are seeing this issue?
Usually verifying "MonitorHealthStatus" agent should help, since this agent calls "Monitor Indicator" activity internally.This activity is responsible for loading all the nodes in AES.
Thanks!
Updated: 4 Jan 2018 14:38 EST
ING Belgium SA NV
BE
Error in logs :
AES:07.30] ( internal.mgmt.Executable) ERROR sbelt10465.devbe.development|XX.XX.XX.XX |SOAP|PegaAES|Events|logAlert|A2D7F4D56BBE951DA56E6391C581EEB3E|Rule-Connect-SOAP.PegaAES-Data-Nodes.ExecuteMBeanOperation - Exception
ING Belgium SA NV
BE
As its fresh installation, only myself is accessing AES now. I could see Agent 'MonitorHealthStatus' is up and running. Is there any checks that i need to do for this issue.
Please advice.
Pegasystems Inc.
US
So here are some troubleshooting tips
Monitored nodes send AES a health status message every two minutes and AES stores it to the health stats table. AES agents process the health stats to create 'indicator' records, and the UI displays indicator records.
On AES server
- be sure that all agents are running
- enable debug logging on parseHealthMessage and parseHLTH0001 activities. Grab the logs and verify that health status messages are coming from the 'missing' monitored node(s)
If you can't find the messages from the server, then we need to debug the monitored node. Enable debugging on httpclient.wire.* classes -- lets be sure that health status messages are going out.