Question


IBM India Pvt. Ltd.
IN
Last activity: 16 Aug 2016 14:08 EDT
AES 7.1 - how to set alert purge frequency / intervals ?
how to set alert purge frequency / intervals in AES?
I don't see any options to set the purge frequency under administartion section. Can someone help me ?
***Updated by Moderator: Vidyaranjan. Removed user added #helpme tag. Apologies for confusion, shouldn't have been an end-user option***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution


Pegasystems Inc.
US
Upon reviewing the associated SR, it was discovered that SA-26500 was generated as a resolution. If you have the same question, please review this SA!


IBM India Pvt. Ltd.
IN
Still looking for help


Pegasystems Inc.
IN
Hi Praveen,
Navigate to Administration > AES Enterprise Administration Tasks > System Settings
Here we can set the limit for either whole cluster or for the particular node.
I have uploaded the screenshot for the same. I hope you are looking for the same.
Let me know on the further concerns.


Pegasystems
IN
You can use the cluster settings to control the retention days.


IBM India Pvt. Ltd.
IN
Thank you Rajiv , I have set these parameters still looks like this is not working as expected. I mean I still see old alerts left in the system. Any other suggestions ?


Pegasystems Inc.
US
Hi Praveen, Have you looked at the AES 7 issue checklist? I think the # 3 (AES Agent execution) might be the issue here. https://collaborate.pega.com/discussion/aes-717-configuration-checklist-n-fold-way-unlimited-clusters


Pegasystems Inc.
US
Hi Praveen,
Be sure the AES agents are running and running successfully, You can see them in SMA and throgh the portal System > Agents (or Agent Schedule) just search for AES.


IBM India Pvt. Ltd.
IN
Thank you Dheer & Jim,
I verified following agents, don't see any issues. Please advise
On AES Node -
On Monitored node :-
Here is the system setting for purge intervals
Thank you Dheer & Jim,
I verified following agents, don't see any issues. Please advise
On AES Node -
On Monitored node :-
Here is the system setting for purge intervals
Still no clue why is the purge not working. Please advise.


Pegasystems Inc.
AU
Please note that the purgeOldData is the agent that is responsible for cleaning the Alerts based on the retention period configured.
The sequence of calls are as follows:
CallcleanupAESAgent -> cleanupAESAgent -> cleanupAESAgent -> purgeOldData.
I suggest you to try the following.
- Verify whether any alerts that exists outside the retention period so that it should be deleted. If yes, these are the alerts that will be deleted when the purgeolddata activity executes.
- Enable debug on the activity purgeOldData.
- Verify whether the following log statement in the pega rules log files. Since, i set the retention period as 14 days, its shows as follows. It also shows the number of records deleted. Since, i dont have anything, the value is shown as blank.
2016-07-31 00:21:55,342 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ AES:07.13] ( purgeOldData.PegaAES_.Action) DEBUG - AES Cleaner beginning purge of PegaAES-Data-Alert using report GetPurgeData for cluster PEGA for retention days 14. Num record:
If the PegaAES-Data-Alert contains the instances that are outside the retention period and still not getting deleted, then i suggest you to raise the Support request.


IBM India Pvt. Ltd.
IN
Thank you Krishnamurthy.
As per your advise I have created a Support Request.
Accepted Solution


Pegasystems Inc.
US
Upon reviewing the associated SR, it was discovered that SA-26500 was generated as a resolution. If you have the same question, please review this SA!