Is there any restriction that we need to configure only these many monitored nodes for AES Server? Also what steps need to be taken care in terms of database performance. I have observed that most of the times the aes tables like pegaam_exception, pegaam_alert,pr_pref_stats all these tables data is getting filled and not getting deleted untill we purge from AES manager portal. Cleaup agent is running with our any exceptions .
What information does the AES Remote agents send to AES. Could any one share some detailed infromation
1)Initialize Health Info Frequency : Every day (86400s)
2)Push Log Usage Data Frequency : Every 10 min
3)Push DB Indexes Frequency : Every day
4)Push Guardrail Data Frequency : Every day
Could any one who worked on AES please provide your suggestions.
Because we are planning to setup our new AES setup in AWS cloud EC2 instance and planning to monitor the SIT and UAT instances (each env has 2 instances for sit and 4 instances for UAT). So more amount of data will be pushed from these nodes to AES. Our DB Memory is 8 GB and storage is 50 GB.
Posted: 5 years ago
Posted: 30 Mar 2017 15:00 EDT
Jim Kelly (JimKelly_GCS)
Senior Manager of Technical Support Engineering
For capacity planning in detail, you should reach out to the Pegasystems Professional Services team that does this every day. There is no one size fits all answer for that question.
That being said you should make sure that the AES agents are running on all nodes of your AES server cluster and that the AES cleanup activities are performed configured out of the box. The AES system settings provide a way to tailor the amount of data that is retained over time should the capacity of your setup fail to allow for the amount of data collected.
There are two recent resources added to the PDN to troubleshoot configuration issues with AES. They may help you as well.