Question
Proximus
BE
Last activity: 16 Mar 2021 6:27 EDT
AES & PEGA 8
Hello,
We've got AES for monitoring our PEGA 7.3.1 applications and recently some PEGA 8.5.2.
AES itself is PEGA 7.3.1 since for what I read there's no upgrade available yet for Oracle (well, I should maybe recheck)
There has been one post already: https://collaborate.pega.com/question/pegaaes-pegaprpc-v8x
This says "you should use PDC". Yet, it's not written as mandatory and I've not seen any planned outphasing of AES.
Some AES DSS have been added with PEGA 8 upgrade. I'm having understanding issues with the below one:
aessetting/RuleUpdatesChange with default value PegaAES/v1/
I'm getting in logs:
The service URL PegaAES/v1/RuleUpdates?cluster_name=MySystemName does not start with a protocol and hostname
In recently upgraded application, Access Group for PegaAESRemote moved to 8 (from 7.10).
Question:
- Can we use AES in 7.3.1 to monitor PEGA 8 ? And to monitor PEGA 7 and PEGA 8 at same time?
- Is there any package to load in AES 7.3.1 itself for monitoring
- What should be the valid URL to put in DSS RuleUpdatesChange
- All agents are disabled but still monitoring & actions are ongoing. AES agents on monitored nodes are no more relevant/used?
Thank you
Regards
Anthony
***Edited by Moderator Marissa to add Product details***
Pegasystems Inc.
US
Proximus
BE
Thank you for the detailed answer.
I was surprised to see AES ruleset upgraded directly while upgrading the application.
I've rolled back this by setting AES Application to point to PegaAESRemote:07-10 instead of 08-05
I can at least just have previous behaviour
Could you please yet clarify URL pattern for RuleUpdatesChange the DSS added?
Thank you
Regards
Anthony
@Anthony_Gourtay
There are no plans at present to release a new version of AES. PDC is preferred solution as it offers you better features, better support and a better price/cost (free!).
AES 83 runs on Platform 8.3 multiTenant and was developed and tested with Postgres and Tomcat. While AES 83 should 'just work' on any application server, there are postgres-specific features for managing data storage using postgres table partitioning. There are clients using AES 8.3 on Oracle - they have accepted responsibility for converting the code to use Oracle partitioning or to manage purge and storage management explicitly.
Platform 852 can send alerts, exceptions and health status to AES 73 or AES 83 - the format has not changed. AES 73 has none of the features to interpret exceptions or raise observations based on PAL stats that are in AES, and will record but not 'understand'' any alert introduced by Platform 74, 81, 82, 83, 84, 85. AES 83 can accept data from platform 85 but will record but not interpret alerts added in platforms 84 and 85.
@Anthony_Gourtay
There are no plans at present to release a new version of AES. PDC is preferred solution as it offers you better features, better support and a better price/cost (free!).
AES 83 runs on Platform 8.3 multiTenant and was developed and tested with Postgres and Tomcat. While AES 83 should 'just work' on any application server, there are postgres-specific features for managing data storage using postgres table partitioning. There are clients using AES 8.3 on Oracle - they have accepted responsibility for converting the code to use Oracle partitioning or to manage purge and storage management explicitly.
Platform 852 can send alerts, exceptions and health status to AES 73 or AES 83 - the format has not changed. AES 73 has none of the features to interpret exceptions or raise observations based on PAL stats that are in AES, and will record but not 'understand'' any alert introduced by Platform 74, 81, 82, 83, 84, 85. AES 83 can accept data from platform 85 but will record but not interpret alerts added in platforms 84 and 85.
All versions of Pega Platform contain a 'PeaAESRemote' ruleset originally created for AES integration now used for PDC integration. The ruleset has always included agents to push usage data and index definitions to AES or PDC. PDC team has enhanced the agents to provide more meta-data regarding the runtime operating environment and added many new agent activities and REST connectors to send data to PDC. Most of the new agent activities are not functional when used with AES 73 - AESRemote will try to call services that do not exist in AES 73. Platform 852 includes a few agents & connector rules to call services added to PDC subsequent to AES 83 completion.