Unable to set up AES in pega
Hi Team ,
I am configuring AES to PEGA. I updated the predictive diagnostic cloud url in Pega and added nodes under class PegaAES-Data-Nodes in AES. But the system node value is not getting updated . Not sure if i missed anything. Please see the screen shots attached.
Accepted Solution
IN
Thanks Abhinav and Sudhakar for your quick in time response. I was able to fix the issue by reindexing the alert and logs AES classes from designer studio.
So issue was elastic search didnt work as reindexing was not done.
Pegasystems Inc.
IN
Hi,
Which version of AES are you installing on top of which PRPC version.There are different procedure till prpc 7.1.6 and above prpc 7.1.6.After looking in the attached image It seems you are facing issue while configuring the nodes.
If you are using prpc 7.1.7+ versions then please follow below steps
Step 1: Create a unique system name and update all nodes
Use the System Name landing page to create the system name and update the corresponding nodes.
1. In Designer Studio, click > System > Settings > System Name to display the System Name landing page.
2. Enter a new system name, and click Submit.
3. Stop and restart the system (all nodes). The new system name takes effect upon restart.
Step 2: Update landing page to send alerts to Pega Autonomic Event Services
1. In Designer Studio, select > System >Settings > Predictive Diagnostic Cloud to display the landing page.
2. Enter the Pega Autonomic Event Services URL.
3. Click “Update Configuration”
Please note that AES is used to monitor PRPC application.There are two steps for AES
1.Installation:Here you have to import jar file.Please follow below document for that
Hi,
Which version of AES are you installing on top of which PRPC version.There are different procedure till prpc 7.1.6 and above prpc 7.1.6.After looking in the attached image It seems you are facing issue while configuring the nodes.
If you are using prpc 7.1.7+ versions then please follow below steps
Step 1: Create a unique system name and update all nodes
Use the System Name landing page to create the system name and update the corresponding nodes.
1. In Designer Studio, click > System > Settings > System Name to display the System Name landing page.
2. Enter a new system name, and click Submit.
3. Stop and restart the system (all nodes). The new system name takes effect upon restart.
Step 2: Update landing page to send alerts to Pega Autonomic Event Services
1. In Designer Studio, select > System >Settings > Predictive Diagnostic Cloud to display the landing page.
2. Enter the Pega Autonomic Event Services URL.
3. Click “Update Configuration”
Please note that AES is used to monitor PRPC application.There are two steps for AES
1.Installation:Here you have to import jar file.Please follow below document for that
https://docs-previous.pega.com/pega-autonomic-event-services-72-installation-and-upgrade-guide
2.Configuration:After installation now you need to configure nodes.These nodes will be monitored by AES.Please follow below document for that.
https://docs-previous.pega.com/pega-autonomic-event-services-72-monitored-node-configuration-guide
IN
Hi Abhinav,
I have already configured the steps 1, 2 i can see my node health of monitored system in AES enterprise services.
But i am not able to see logs or alerts in AES for monitored system I verified the AES agents and restarted them they are up and running.
Still i could not see the logs.
Please help.
Pegasystems Inc.
IN
Hi Pavani,
When did you have configured the nodes.There are some agents which runs at night so please wait fore one day and verify tomorrow.
Meanwhile you can verify contents of below tables ,AES fetches data from monitored nodes and stores them in these tables.
pegaam_node_health:These records used to generate data in enterprise health console
pegaam_node_stats
pegaam_alert-:Most of the details are similar to alert log
pegaam_action_work
pegaam_exception
pegaam_exception_work
Pegasystems Inc.
IN
If you are using prpc version prior to 7.1.6 then you need to do changes in prconfig.xml and prlogging.xml.Did you verify the tables mentioned above?
Accepted Solution
IN
Thanks Abhinav and Sudhakar for your quick in time response. I was able to fix the issue by reindexing the alert and logs AES classes from designer studio.
So issue was elastic search didnt work as reindexing was not done.